Release Notes for JMRI 4.23.4 release
Date: April 20, 2021
From: Bob Jacobsen
Subject: Test Release 4.23.4 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 next in a series of test releases.
We expect this series to end in the next JMRI production release in Summer 2021.
(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 release 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.
Update From Older JMRI Versions
If you are currently using a version older than JMRI 4.20, please follow these instructions carefully:
- Is your current version older than JMRI 4.12?
If so, then update to JMRI 4.12 first, and ensure everything works correctly: check
start-up, check things you need to be working, and check the JMRI log as well) before doing anything else.
Store your configuration and panel files under a new name and use those from now on.
Then continue with step 2.
If you are currently using JMRI 4.7.3 or earlier on Linux or macOS (Windows doesn't need this),
then it's very important
that you update to JMRI 4.12 and
carrying out the migration process described in the JMRI 4.12 release note
before updating to any later relese.
- Is your current version older than JMRI 4.20?
Then update to JMRI 4.20 first, and ensure that works correctly (check
start-up, check things you need to be working, and check the JMRI log as well) before doing anything else
Store your configuration and panel files under a new name and use those from now on.
- You can then install this release.
Following this multi-step order of updating via stable major releases safeguards you against possible migration issues
that can arise from skipping these versions.
New problems with this release
New warnings for this release:
Older warnings
See the
JMRI 4.20 release note for more warnings predating the 4.21 development series,
including pointers to various migration issues.
These may be relevant to you if you're updating from an earlier version;
we strongly recommend you update to
JMRI 4.20
installing this test release.
- Since JMRI 4.21.1
The jmri.jmrix.SystemConnectionMemo class has become a jmri.SystemConnectionMemo
interface and a jmri.jmrix.DefaultSystemConnectionMemo class. This may
require changes to scripts. If you have a script that references
jmri.jmrix.SystemConnectionMemo, please change it to either
jmri.SystemConnectionMemo or jmri.jmrix.DefaultSystemConnectionMemo
(it's easier to have you just try the two than to explain which
one will work in which case)
- Since JMRI 4.21.1
The way preferences are loaded at startup has been slightly
modified. There is no impact to JMRI applications, but Non-JMRI
applications that are not derived from apps.Apps or apps.AppsBase
but are using jmri.implementation.JmriConfigurationManager to load
preferences will no longer see preferences if an error occurs. To
restore the old behavior, use apps.AppsConfigurationManager instead.
- Since JMRI 4.11.4
There are issues with the Pi-SPROG One command station operation. A number of workarounds should be applied:
- Do not turn on the track power until the power supply to the Pi-SPROG ONE is turned on
- Do not enable extra debugging through default.lcf, nor open the system console window
- Do not open the SPROG console window
- Disable power conversion (CV 29) in all locos
- If connecting via VNC (or similar), setup the screen layout before turning on the track power
Pi-SPROG One with version 2.4 or earlier firmware will cause a timeout after a track short circuit. A dialog box will
open to inform the user of this. The track power will be turned off and must be turned on again using the power control.
Download links:
The
list of included changes is available from our
GitHub code repository.
Hardware Support
CBUS
- CANPiWi v1 Firmware - No need for Node Manager to request Number of Events.
- Fixed Internal Sensor Manager set as default, not CBUS Sensor Manager, affecting 4.19.6 onwards.
- DCC Programmer - Added support for hardware that supports CV read hints
DCC++ and DCC-EX
- DCCppOverTCP server now forwards all messages, even those with unknown or invalid syntax
SPROG
- Added startup action to open SPROG Slot Monitor
CTC Tool
- The CTC Editor windows location and size settings have been moved to the
standard JMRI location within the current profile. The AwtWindowProperies.txt
file in the ctc directory at the user files location is no longer used.
Layout Editor
- Labels and icons on a panel can now have an Id. This is useful if the label/icon is controlled by LogixNG.
LogixNG
- Add Actions and Expressions for Blocks.
- Add Actions for labels and icons on panels.
- Add support for WhereUsed bean usage searches.
- Add WhereUsed reports for Blocks and Sensors.
Control Panel Editor
- Labels and icons on a panel can now have an Id. This is useful if the label/icon is controlled by LogixNG.
Turnouts, Lights, Sensors and other elements
- Fixed Duplication of Sensors in Sensor Table views. Bug introduced in 4.23.3
- Fixed Sensor Table sort issues with Delay to Active, Delay to InActive columns.
Scripting
Throttle
- When "Use large speed slider and control buttons" is enabled, throttle control panel buttons (and slider) will resize automatically to leverage available space in throttle control panel
Where Used
- Add support for searching LogixNG for bean usage.
Miscellaneous
- Automatic Signal Mast Logic Production: Corrected to use Protecting Blocks
- Transit Creation Tool: Uses block sections on transits emanating from stubs.
