Jmri conditional systemname2/12/2024 ![]() Peter Ulvestad updated the Bachmann EZDCC decoder definition to put a max value on CV2. Marc Founier added and updated MRC Athearn decoder definitions. Peter Ulvestad updated the MRC Sound Brilliance 1806 decoder definition. Mark Fournier updated the Comprehensive programmer to handle more consisting options. Panel Editor icons can be edited directly from the Panel by selecting the "edit" item from the popup menu of the icon. Paul Bender added "invert" capability to XPressNet turnouts. Pete Cressman added the capability to edit (change) the icons used by a particular item on a Panel Editor panel Ken Cameron updated the decoder definition for the Team Digital SMC4.įixed a problem when using the invert option on LocoNet sensors. The warning is that files written in thisįormat will not be properly read by JMRI versions before 2.7.4.įrom earlier versions that are read by JMRI 2.7.4 or later and then written out again,Īs the program will update them to the new format upon storing them. Keep all your files in the JMRI preferences directory on both machines, the files Panel files from one computer to another, even of a different type. The advantage is that this new method will make it much easier to move JMRI 2.7.4 changed the way filenames for icons, etc, are stored in XML files by JMRI. We've created a tool to make that easier.įor information on how to use that tool, please see the You should migrate those roster entries to the new decoder definition names. If your roster contains locomotives with Soundtraxx Steam Tsunami decoders, In particular, if you'veĬreated your own copies of startup scripts, you'll have to update those: The 2.7.4 and earlier scripts will not work with 2.7.5 and later. Startup scripts include the new libraries, so these have also been modified. Those libraries are included in the JMRI downloads. The new audio support in JMRI 2.7.5 requires some new libraries. ![]() In turn, this means that if you've created your own startup scripts, you may need JMRI 2.7.7 uses a different set of libraries for processing the XML panel files. Throttle classes themselves) may cause trouble for scripts that were using them. You select this at the bottom of the window when openingĪ locomotive for editing, or via the JMRI Preferences window.Ĭhanges in JMRI 2.7.7 to the internal structure of the classes for the throttle windows (not the If you want to use the "Function Label" or "Roster Image" panes with theĭecoderPro "Comprehensive" programmer format, you should change to using See the XmlFile Javadoc for more information. On users, but might effect people who have written scripts to ![]() XML input processing was reworked in JMRI 2.7.8. ![]() For more information, pleaseĬopyright and licensing page. Many new decoder definitions, several new hardware connections, andĪ number of new system customization tools.Greatly improved Logix, signaling, operations, editors, and other tools.Greatly improved throttle support, with more flexibility for customization, locomotive images, andĪbility to use iPhones, iPods and Wii remotes as throttles.We're therefore making that version, "Production version 2.8" available for download today.Īmong the enhancements since the last production release, JMRI 2.6, are: Version that's good enough to be recommended for general use, including by new users. We are very pleased to announce that the 2.7 series of JMRI test releases has resulted in a Subject: Production release 2.8 of JMRI/DecoderPro is available for download. Supported Hardware Devices, command stations, networks, and protocols: Debugging an installation Release Notes.Download and install JMRI® JMRI Setup and Installation JMRI environments.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |