Release Notes for JMRI 4.5.7 release
Date: Nov 30, 2016
From: Matthew Harris
Subject: Test version 4.5.7 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 the next in a series of test versions. We expect this series to end in the next JMRI production release around the end of 2016. (See the tentative release schedule)
Some of the changes involved are quite extensive. They may require a certain amount of experience before they are working well. Therefore, this test version should be considered experimental.
Known problems with this release
- When a Digitrax DCS240 is the command station, JMRI throttles may not be able to take control of a locomotive or consist in some cases if the DCS240 "expanded slots" (i.e. 400 slots) feature is in use. Be sure to "dispatch" or "release" locomotives and consists from throttles which use "expanded slots" before attempting to acquire the locomotive or consist via a JMRI throttle, as this may enable JMRI to acquire the locomotive or consist. This problem can affect throttles which use the JMRI WiThrottle interface and throttles controlled via the JMRI Web Server. This issue is thought to be present in all previous versions of JMRI.
- DCC++ connections on Linux may not work.
New warnings for this version:
- None yet
Older warningsSee the JMRI 4.4 release note for warnings predating the 4.4 development series. These may be relevant to you if you're updating from an earlier version.
(Since JMRI 4.5.6) As part of fixing the TMCC throttle issue, the handling of TMCC preferences was changed. If you have a TMCC connection configured, please go to the "Defaults" pane in the Preferences window and make sure that the TMCC connection is selected for the appropriate device types.
(Since JMRI 4.5.5) Apple has released a new "Sierra" version of macOS (formerly known as OS X) which has enhanced security for downloaded programs. We're providing a new form of signed download to work with this, see below. We'd be interested to hear whether that download works on older OS versions, so that we can just release this new form without having to provide separate downloads.
(Since JMRI 4.5.2)This and future versions of JMRI may not function on OS X if the Java SE 6 provided by Apple is installed. OS X operating system updates routinely remove this version of Java SE 6. Please raise any issues concerning this on the user's group.
To remove Java SE 6 from OS X, follow these steps (these steps assume JMRI is installed in the folder /Applications/JMRI, if not, adjust the following paths as needed):
- Open Terminal.app.
El Capitan only: Reboot into Recovery Mode by restarting your Mac and pressing Cmd-R until the Apple logo appears. Once in Recovery Mode, select Terminal from the Utilities menu.
- Run the command
/Applications/JMRI/PanelPro.app/Contents/Resources/uninstall-java6.shIt can take up to a half hour to complete. Wait for the message Removed Apple Java SE6.
El Capitan only: Run the command
bash /Volumes/Macintosh\ HD/Applications/JMRI/PanelPro.app/Contents/Resources/uninstall-java6.sh /Volumes/Macintosh\ HDIt can take up to a half hour to complete. Wait for the message Removed Apple Java SE6.
- El Capitan only: Restart your Mac.
(Since JMRI 4.5.2)Support for directly executing AppleScript within JMRI has been removed due to changes in macOS and Java outside our control. If you require the ability to use AppleScript, you may be able to add this capability on your own by visiting JMRI AppleScript Support, but please be aware that this may not work on upcoming releases of macOS or Java.
(Since JMRI 4.5.1)LocoTools, no longer supported since JMRI 2.10, has been removed from the Linux and OS X distributions.
(Since JMRI 4.5.1)Internal turnouts and sensors need to have complete, individual system names. The names "IT" and "IS" (without any suffix) are no longer permitted: "IT12" is fine, but just "IT" is not. Most panel files that contain these should automatically migrate them to new names when saved, but in some cases you might need to manually update them.
(Since JMRI 4.3.5) When sharing a configuration between this version and JMRI 4.3.4 or older, the older version of JMRI will not reflect changes in preferences, window position, table sorting, column order, or other user interface state. This is due to changes in how user preferences and interface state are stored.
(Since JMRI 4.3.3) You can now set the order of your startup items: If you're opening panel files, running scripts, etc as the program starts up, there's a preferences pane that lets you easily set the order in which those happen. If you've set the order manually (e.g. by editing configuration files) in the past, please check this preference to make sure it's set the way you want.
(Since JMRI 4.1.2) Jython has been upgraded to version 2.7.0 with the following potentially breaking changes:
- The decodeJmriFilename() function is no longer available by default. Use the FileUtil.getExternalFilename() method instead.
- The simple propertyListener object is no longer available by default. Create your own, following the examples provided in the jython folder in the JMRI distribution.
- jmri_defaults.py included in the JMRI distribution is no longer executed by default, but will be executed before any other Jython scipts if included in your User Files location.
- The default behavior of python.cachedir.skip is now true. If using a custom python.properties file, include "python.cachedir.skip=false" in that file.
- Certain Python scripts are too large to be evaluated in Jython. If a script fails with the
java.io.IOException: Mark invaliderror, set "jython.exec=true" in a custom python.properties file or rewrite the script to be less than 100,000 characters per file. Note that when using "jython.exec=true" it may be desirable to run the included script jmri_bindings.py as a startup action to emulate the evaluation environment used when jython.exec=false.
(Since JMRI 4.1.1) Decoder definitions that use the "ivariable" form are now deprecated. Definitions included with this release have been converted to the new form. If you have decoder definitions with the older "ivariable" form, they will no longer validate, but can still be used for the first couple of test releases in this series. Please ask on the JMRI users Yahoo group for help converting them, or just drop them and use the current definitions.
Please use these links for downloading:
OS X: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.4.5.7-R3265cd6.dmg/download
Changes since test release 4.5.6:The list of included commits is available from our GitHub code repository.
- User interface improvements in the Configuration dialog. The dialog will now use an advanced and much faster algorithm to load the initial values of the configuration from the hardware. Users should not need to use the "Read All" button anymore. Changed values are now highlighted in similar way as DecoderPro does. The configuration dialog opens immediately and shows the progress as the XML data is downloaded via the network. It is also possible to re-try loading if the first load fails. A cache allows opening the same dialog instantly for the second time.
- Fixed a software problem that lead to multiple issues when CPU load is high, such as failed firmware downloads or inability to open the configuration dialog. On some systems it was enough to have the OpenLCB Monitor window open to trigger the problem.
New / Updated decoder definitions
- None in this release
- Fixed a problem with adding Train/loco icons to the panel
- Fixed an issue to set aspects in the Signal Mast Table using the combobox. Sorting rows or moving columns in the table is fully supported.
- A bug when Calibrating a throttle speed factor in NXWarrants has been fixed.
- SCWarrants are converted to regular Warrants with a "No Ramping" flag set. Such warrants change speed as before upon entering the approach block. Now they use the speeds specified by the signals rather than one hard coded value. The new "No Ramping" flag may be turned off and on in the Warrant Editing window.
- The MS Windows launcher has had a number of updates including:
- a new method to calculate the maximum memory
- use the Windows look and feel as an initial default
- allow the classpath to be modified by either appending `--cp:a=CLASSPATH` or prepending `--cp:p=CLASSPATH`
- allow for default options to be specified in a `jmri.conf` file stored in `%userprofile%\JMRI`