Release Notes for JMRI 3.9.6 release
Date: December 7, 2014
From: Bob Jacobsen
Subject: Test version 3.9.6 of JMRI/DecoderPro is available for download.
This is a test release. Please post a note if you encounter any new or old bugs! And please back up your JMRI files before installing this, in case you want to go back to an earlier version.
This is one of the last in a series of test versions. We expect this series to end in a JMRI 3.10 production release around the end of 2014.
New warnings for this version:
Older warningsThe JMRI 3.9.* releases series, including this one, and JMRI 3.10 (expected in December 2014), will be the last JMRI releases that will work with Java 1.6. To use any later JMRI test or production releases, you'll have to update the Java on your computer to Java 1.8 or later. All JMRI releases 3.9.3 and are tested on Java 1.8, so you can do the Java update now if you want to.
The 3.9.5 release had some changes to XML file processing. They're meant to be transparent for existing files (roster, panels, etc), but mistakes happen. If you encounter trouble with existing roster or panel files, please let us know. Most importantly, if that happens, immediately make a back up copy of your files!
RFID support has been changed to allow for additional protocols - existing CORE-ID readers should remain unaffected but, in certain circumstances, it may be necessary to update connection configuration with the correct protocol.
The activation.jar library is no longer included with the JMRI download. This shouldn't have any impact on you, but it's remotely possible that it might impact you if you have your own Java code that you're combining with JMRI and/or you're still using a Java version before Java 1.6. (Scripts and panel files will not be impacted.)
Images associated with roster entries are now saved to the roster directory instead of the resources directory when added to the roster entry. Existing images are not moved.
The XmlIO web service has been deprecated and is scheduled to be removed after JMRI 3.12 (July 2015). All users and developers who are relying on direct access to the XmlIO API are recommended to begin using the JSON API. inControl web throttle users are recommended to begin using webThrottle instead, or to plan on investing in devices that can support webThrottle, WiThrottle for iOS, or Engine Driver for Android.
Several methods in the InstanceManager class have been deprecated and will be removed after JMRI 3.12 (July 2015). This doesn't affect JMRI users, but if you have your own code that uses JMRI, please take a look at the code and make any necessary changes.
Known problems with this release
None at this time.
Please use these links for downloading:
Changes since test release 3.9.5:
New / Updated decoder definitions
- A problem in the QDecoder ZBasic definition was fixed.
- Decoder definitions can now be written for accessory decoders that use accessory ops mode programming. See the xml/decoders/0NMRA_accessory.xml file for an example. This is new support which needs more work and testing. If you have one of these decoders and want to help, please contact us.
- Peter Ulvestad fixed some spelling errors in BLI Blueline decoder definitions.
- Fixed a problem with addresses in some older TCS BEMF decoders
- Additional icons in the USS series
- Fixed a problem with the Approach aspect and diverging in the basic signal set
- The Python interpreter is now initialized on demand, when first used. If the former default behavior of initializing the Python interpreter during application launch is required, include -Dorg.jmri.python.preload=true in the JMRI_OPTIONS environment variable.
- It is now possible to influence the initialization of the Python interpreter by setting Jython and Python properties in the file "python.properties" in a Configuration Profile directory, or in the JMRI Settings directory.
- A Jython interpreter must be in the Java CLASSPATH. JMRI is shipped with a Jython interpreter, so unless the JMRI installation is modified, one should be available.
Dan Boudreau made the following changes to operations:
- New feature. You can now manually select a background color for a train's row in the "Trains" window. There's also an "Auto" option that allows you to select a background color for when a train is built, build fails, or is terminated. See under Tools in the Trains window "Trains Table Colors".
- Removed in manifest and switch list title any references to "manifest" or "switch list". Now manifests and switch lists text is completely under the control of a user.
- LocoNet turnouts that use EXACT feedback now transition through INCONSISTENT as they move from THROWN to CLOSED or CLOSED to THROWN.
- SE8c signal heads now try to track the layout status to detect changes in their state caused by external events, e.g. something outside JMRI changing them. This is useful when e.g. you've got two computers controlling a LocoNet. Note that this works for RED, YELLOW, GREEN and DARK, but not for the FLASHING aspects, nor for Held and Lit states. The recommendation is still to have all your layout Logix running in a single running copy of JMRI.
- NCE Network Connection method fixed to enable the different NCE menu items. (Ken C)
- RFID support has been added for Seeed Studio RDM630 readers. (Matthew Harris)
- Walter Thompson improved the LocoNet stats help.
- Improved handling of long vs short in AbstractAutomat scripting