Skip to main content

Release Notes for JMRI 2.11.7 release

Date: June 15, 2011

From: Bob Jacobsen

Subject: Test version 2.11.7 of JMRI/DecoderPro is available for download.

Notes:

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 seventh in a series of test versions. We expect this series to end in a JMRI 2.12 or 3.0 production release in 2011.

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.

JMRI is now only available under the GNU General Public License. For more information, please see our copyright and licensing page.

New warnings for this version:

(None yet)

Older warnings

Development Version 2.11.4 contains significant improvements to the Powerline Interfaces. Some of these improvements involved a complete restructuring of the underlying code. As a result, previously working Preferences may now show no connections for some of the Powerline Interfaces. If this occurs, go to Preferences and setup the Powerline Layout Connections again. Then save the Preferences and restart JMRI.

In Development Version 2.11.3 JMRI instituted a more robust and transparent system for handling missing panel icon files. If missing icon files are discovered during the panel loading process this system presents a dialog box that allows the user to either delete the offending reference or use the file browser to find the proper location. Older versions of JMRI didn't always fully remove the references to deleted panel icons. Panels which contain these stray references will present the dialog box during the first panel load. If the panel worked fine before, simply choose the delete option for each "missing" icon presented to remove the stray references. Once the panel has finished loading, save/store the panel file, quit JMRI and then reload. As a precaution, we recommend either making a backup copy of your panel file before diving in or saving the modified file under a different name

There have been extensive changes to the throttle code. If you have written scripts that use throttles, particularly multiple throttles, please check to make sure they still work.

The numerical values of "ON" and "OFF" for Lights changed in JMRI 2.11.2, along with some of the other constants in the class. This will have no impact on people just using the program. If you're using scripts with numerical values in them, please recode them to use the symbolic values.

Known problems with this release

None at the time of this release.

Download links:

Please use these links for downloading:

Mac OS X: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.2.11.7.dmg/download

Windows: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.2.11.7.exe/download

Linux: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.2.11.7.tgz/download

Changes since test release version 2.11.6

Paul Bender added a Consist Manager for LocoNet with the following notes on it's current capabilities and known issues: Basic functionallity of adding and removing locomotives from consits is working, however there are several known issues with this release: 1) The check boxes for changing the direction of a locomotive within a consist are not working 2) The delete button at the bottom of the throttle does not work correctly. 3) You cannot currently add an existing lead address (created with the tool) to another consist. 4) The consist manager does not currently examine the slots for consists

Dan Boudreau

New operations features and bug fixes:

Pete Cressman

Fixed the NCE consist editor, broken since 2.11.4.

Bob Jacobsen fixed a problem with checkboxes and indexed variables in DecoderPro. No decoders were using it yet, but several are about to, so this will be needed for new decoder types. At the same time, an "issue" with sizing of indexed enum variables was fixed. Some decoder definitions may have been counting on the buggy behavior for their layouts, so if you see any decoder definitions that look messy now, please mention it in the jmriusers group.

Kevin Dickerson