/
jmri4.2.shtml
676 lines (604 loc) · 37.9 KB
/
jmri4.2.shtml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>
JMRI: Release Notes for 4.2
</title>
<meta content="Bob Jacobsen" name="Author">
<meta name="keywords" content="java model railroad JMRI 4.2 decoderpro panelpro loconet lenz nce easydcc dcc nmra">
<!-- Style -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" type="text/css" href="/css/default.css" media="screen">
<link rel="stylesheet" type="text/css" href="/css/print.css" media="print">
<link rel="icon" href="/images/jmri.ico" type="image/png">
<link rel="home" title="Home" href="/">
<!-- /Style -->
</head>
<body>
<!--#include virtual="/Header" -->
<div class="nomenu" id="mBody">
<div id="mainContent">
<h2>
Release Notes for JMRI 4.2 release
</h2>
<p>Date: December 25, 2015</p>
<p>From: Matthew Harris</p>
<p>Subject: Production version 4.2 of JMRI/DecoderPro is available for download.</p>
<!--<p><b>This is a draft release note only; the download links do not yet work</b></p>-->
We are very pleased to announce that the 4.1 series of JMRI test releases has resulted in a
version that's good enough to be recommended for general use, including by new users.
We're therefore making that version, "Production version 4.2" available for download today.
<h3>Notes:</h3>
<p><b>
JMRI is now only available under the
<a href="/COPYING">GNU General Public License</a>. For more information, please
see our
<a href="/Copyright.html">copyright and licensing page</a>.</b></p>
<h3>Known problems with this release</h3>
<p>MacOS X cannot show most connections correctly. As a workaround, this can be fixed by running the command
<code>sudo find / -name StartJMRI -type f -exec sed -i "" -e 's/\/dev\/tty\\\.\*//' -e 's/\/dev\/cu\\\.\*//' {} \;</code>
in Terminal.app. It will ask for your password, and, after a couple of minutes, have fixed the issue.</p>
<p>The Digitrax PR2 does not work with this release. If you need to work with a
PR2, please stay with <a href="jmri4.1.3.shtml">JMRI 4.1.3</a> or earlier,
or wait for <a href="jmri4.3.1.shtml">JMRI 4.3.1</a> which should appear in December 2015.
<p>Fixes for these problems will be in
<A href="jmri4.3.1.shtml">JMRI 4.3.1</a>, due out soon after this release,
or pick up a
<a href="http://builds.jmri.org/jenkins/job/Development/job/Packages/">development build installer</a>
from
<a href="http://builds.jmri.org/jenkins/job/Development/job/Packages/">Jenkins</a>.</p>
<a id="warnings" name="warnings"></a>
<h3>Warnings:</h3>
See the <a href="jmri4.0.1.shtml#warnings">JMRI 4.0.1 release note</a>
for older warnings that may be relevant to you if you're updating from an earlier version.
too.
<p>We are now building releases, including this one, from our
<a href="https://github.com/JMRI">GitHub repository</a>.
For more information on this, please see our
<a href="http://jmri.org/help/en/html/doc/Technical/getgitcode.shtml">documentation page</a>.
<p>The configuration is now stored in multiple files within a directory named <code>profile</code>
inside a Configuration Profile instead of within the file <code>ProfileConfig.xml</code>.
PanelPro and DecoderPro both should migrate from the old configuration to the new configuration seamlessly.
See JMRI <a href="https://github.com/JMRI/JMRI/issues/69#issuecomment-155385101">Issue #69</a> for more details.
Please report any issues at <a href="https://github.com/JMRI/JMRI/issues/new">our GitHub project</a>.</p>
<a id="decoderSchema" name="decoderSchema"></a>
<p>The <a href="http://jmri.org/xml/schema/decoder.xsd">XML schema</a>
for decoder files has been made more precise.
This shouldn't effect people who just use the JMRI decoder definitions as distributed,
because they all work with this more precise version. But if you have decoder
definitions of your own, you may have to update them. Ask for help on
<a href="https://groups.yahoo.com/neo/groups/jmriusers/info">JMRI users</a>
if you have trouble.
Specifically, the decoder file verification will now reject a few things
that it didn't catch before, even though they didn't really work:
<ul>
<li>There can be only one label element for a given language on a given variable.
<li>A variable element has to contain just one type element such as decVal, enumVal, etc.
</ul>
As a side effect of checking this, the qualifier elements inside a variable now have to
be at the front of the contents, and the label, comment and tooltip elements have to be
at the back. You can't just sprinkle them around and hope the code finds them
(because sometimes in the past the program would miss one; now we require an order we're
sure the code will understand).
<p>The code for handling Panel Editor / Control Panel Editor icons has changed
to better deal with rotating icons. This has changed how opaque vs transparent
icon backgrounds are handled. Please check your panels to make sure we
haven't inadvertently caused a problem, particularly if you've got rotated
icons and/or use have custom icons with transparent backgrounds. If there
are any problems, please send in a copy of your panel file so we can
recreate the problem and fix it.</p>
<!-- retain through 4.2 -->
<p>Mac OS X 10.11 El Capitan requires signed drivers for USB adapters. If you've upgraded
from an earlier version, your drivers may not work. That will cause JMRI to throw errors
when it doesn't find communications links. To fix this, go to the web site for your
adapter manufacturer, find the drivers that are listed to work with Mac OS X 10.9 or later,
download, and install, then retry JMRI again.
<p>RFID readers using the Olimex protocol were incorrectly decoding tag values - this has
now been fixed. If you were using Olimex RFID readers with earlier versions, your existing
ID Tag database will contain invalid tags. New ID Tag entries will be generated for each
correctly read tag - this will require that any additional information be re-entered and,
optionally, old invalid entries manually deleted.</p>
<p>Jython has been upgraded to version 2.7.0 with the following potentially breaking changes:</p>
<ul>
<li>The decodeJmriFilename() function is no longer available by default.
Use the FileUtil.getExternalFilename() method instead.</li>
<li>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.</li>
<li>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.</li>
<li>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.</li>
<li>Certain Python scripts are too large to be evaluated in Jython.
If a script fails with the <code>java.io.IOException: Mark invalid</code> error,
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.</li>
</ul>
<p>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
<a href="https://groups.yahoo.com/neo/groups/jmriusers/info">JMRI users Yahoo group</a>
for help converting them, or just drop them and use the current definitions.</p>
<p>The OpenLCB 0.6.4 library in this version has a bug in its alias
calculations which prevents JMRI from communicating occasionally.
A patch has been submitted to the OpenLCB group, but as they seem no longer interested in maintaining that code, it's not known when this will be fixed.
In the meantime, the workaround is to restart JMRI and/or the hardware node(s)
and try again; that might allocate different alias values.</p>
<h3>Download links:</h3>
<p>Please use these links for downloading:</p>
<p>Mac OS X: <a
href="https://sourceforge.net/projects/jmri/files/production%20files/JMRI.4.2-R6f3c1be.dmg/download">https://sourceforge.net/projects/jmri/files/production%20files/JMRI.4.2-R6f3c1be.dmg/download</a><br/>
sha256: 7503308fcf8c17dc62b345016c439f986d62341cc5feb8e33e53b64414ca0358</p>
<p>Windows: <a
href="https://sourceforge.net/projects/jmri/files/production%20files/JMRI.4.2-R6f3c1be.exe/download">https://sourceforge.net/projects/jmri/files/production%20files/JMRI.4.2-R6f3c1be.exe/download</a><br/>
sha256: 43baa7f2dea96924595882f778034f6ef86c99f74a16a766fe271d2295b6a316</p>
<p>Linux: <a
href="https://sourceforge.net/projects/jmri/files/production%20files/JMRI.4.2-R6f3c1be.tgz/download">https://sourceforge.net/projects/jmri/files/production%20files/JMRI.4.2-R6f3c1be.tgz/download</a><br/>
sha256: 76cb4293ab9016f037ddfb67e04918af41eae3e967b6a22b8921d42add21aac8</p>
<!--
Preliminary build files (not the final released files) can be found
on the
<a href="http://builds.jmri.org/jenkins/job/Test%20Releases/job/4.2/ws/dist/release/">CI project page</a>.
-->
<!--
<p>During development leading to the actual release, you can find test download files on the
<a href="http://builds.jmri.org/jenkins/job/Development/job/Packages/">continuous integration build page</a>.
These are development files, and might not be working at any particular time.</p>
-->
<h3>Changes since test release 4.0:</h3>
<h4>Hardware Support</h4>
<p>Improved error handling during start-up when something Really Unexpected
happens, such as configuring to connect to a port that doesn't even exist.</p>
<h5>C/MRI</h5>
<ul>
<li>You can now connect to your C/MRI nodes via a
<a href="http://jmri.org/help/en/html/hardware/cmri/CMRI.shtml#net">network connection</a>.</li>
</ul>
<h5>DCC++</h5>
<ul>
<li>NOTE: DCC++ Support is broken in 4.2.0. Sorry! If you need DCC++ support, please revert to 4.1.5 or wait for 4.3.1</li>
</ul>
<h5>JMRI Simple Server/JMRI Client</h5>
<ul>
<li>Fixed bugs in both the JMRI Simple Server and JMRI Client
that prevented reporter information from being passed from
the server to the client.</li>
<li>Fixed bugs in both the JMRI Simple Server and the JMRI
Client that caused the server crash when a lower case
letter was used in the transmitted prefix.</li>
<li>Make client attempt to reconnect if the connection is
closed unexpectedly.</li>
</ul>
<h5>LocoNet</h5>
<ul>
<li>JMRI can now directly program LocoNet devices that use the
"System Variable" (SV) protocol version 2. Select
"<a href="http://jmri.org/help/en/html/hardware/loconet/Addressing.shtml#SVs">System Variable Type 2</a>"
as a
<a href="http://jmri.org/help/en/package/jmri/jmrit/simpleprog/SimpleProgFrame.shtml">Single CV Programmer</a>
mode to use this, and see
<a href="http://jmri.org/help/en/html/hardware/loconet/Addressing.shtml#SVs">this page</a>
for more details.
<li>More work on the LN SV2 programming protocol.
Please see the
<a href="http://jmri.org/help/en/html/hardware/loconet/Addressing.shtml#SVs">documentation page</a>.
It's basically ready for people to
start defining board definition files.
A basic definition is available
under "Public Domain and DIY" decoders, then
"LNSV2-using boards".</li>
<li>LocoNet Monitor now decodes LN SV2 programming protocol messages.</li>
<li>A programmer mode for the original LocoIO boards,
which use the LN SV1 programming protocol,
is <a href="http://jmri.org/help/en/html/hardware/loconet/Addressing.shtml#SVs">also available</a>.
A basic DecoderPro decoder definition is available
under "Public Domain and DIY" decoders, then
"Hans De Loof LocoIO".</li>
<li>You can now configure a connection to a
<a href="http://www.mollehem.se/index.php/electronics/smartphoninterface-detail">Bluetooth LocoBridge adapter</a>
in the Digitrax connection preferences.</li>
</ul>
<h5>NCE</h5>
<ul>
<li>Configure USB Tool - Removed attempted reading of the current USB cab id.
It was not working for all cases and prevented reseting the cab id
when the USB had an invalid (for the system currently connected) cab id.</li>
<li>Dave Heap added display of USB & Serial computer cab context pages
to the NCE Cabs Monitor.</li>
</ul>
<h5>OpenLCB</h5>
<ul>
<li>The OpenLCB library advanced to version 0.6.4, which (among other things)
fixed a problem when trying to read broken configuration definition info
from a node.
<p>
Note that this is probably the last version of this library, as
prototype work is no longer a part of the OpenLCB group effort.
It's not yet clear whether a new group will emerge to maintain
this code. If you're interested in helping, please contact
the JMRI or OpenLCB developers.
</li>
<li>The basic work to allow programming of OpenLCB Nodes via the
DecoderPro infrastructure is in place. Later updates will
connect this to DecoderPro itself.</li>
<li>A basic
<a href="http://jmri.org/help/en/package/jmri/jmrix/openlcb/swing/downloader/LoaderFrame.shtml">bootloader</a>
is available for attached OpenLCB nodes.
This lets you install new firmware in a compatible node from
a local .hex file (provided by the node manufacturer). Nobody
has announced nodes that use this feature, but hopefully since we
built it they will come.
<p>
Note: For safe and reliable operation, this relies on items
that were removed from the OpenLCB specification in February 2015.
For more information, see the
<a href="http://jmri.sourceforge.net/JavaDoc/doc/jmri/jmrix/openlcb/swing/downloader/package-summary.html">package documentation</a>.
</li>
<li>The OpenLCB support library has been updated to version 0.6.5</li>
</ul>
<h5>RFID</h5>
<ul>
<li>Network connections to RFID readers are now possible. Each connection
configured into JMRI can talk to a single RFID reader, or to multiple ones
through a MERG-style concentrator or equivalent. JMRI can have
as many RFID readers connected via network connections as desired.</li>
<li>Oscar A. Pruitt provided the implementation to support RFID readers using
the EM-18 protocol</li>
<li>A bug that caused connections using the MERG Concentrator to not work has
been fixed. (Matt Harris)</li>
<li>A bug that meant RFID tags were misread when using Olimex RFID readers has
been fixed. This will mean that details of any existing tags read using an
Olimex reader are now invalid and will need to be re-identified and updated
in the ID Tag list. (Matt Harris)</li>
<li>Minor corrections were made in the Core-ID, EM18 and SeeedStudio RFID reader
interfaces to correctly reject any tag reads with invalid checksums - this
was not always happening resulting in the potential of incorrect tag reads
being accepted. (Matt Harris)</li>
<li>Added test cases for all implemented RFID protocols. (Matt Harris)</li>
</ul>
<h5>SPROG</h5>
<ul>
<li>Dave Heap made the following changes:<br>
<ul>
<li>Modified the SPROG Command Station code to work around issues
with some non NMRA-compliant decoders.</li>
<li>The SPROG Programmer now correctly reports an overload on the
Programming Track.</li>
</ul>
</li>
</ul>
<h4>Signals</h4>
<h5>Signal Mast Editor</h5>
<ul>
<li>Ken Cameron fixed editing of signal head masts to also support old format
panel files.</li>
<li>Dick Bronson updated the NS 2008 definition</li>
</ul>
<h4>New / Updated decoder definitions</h4>
<p>The
<a href="http://jmri.org/xml/schema/decoder.xsd">XML schema</a>
for decoder files has been made more precise.
See the
<a href="#decoderSchema">warning above</a>
for more on the implications of this.
<ul>
<li>Dave Heap made the following changes to Factory Resets:<br>
<ul>
<li>A preferred programming mode for the reset can be specified and will
be used if available.</li>
<li>Programming on Main mode for the reset will now be available if explicitly
specified for a decoder.</li>
<li>These features are made available by specifying <mode> elements for
<resets>, <factReset> or <ifactReset>.
</li>
</ul>
</li>
</ul>
</p>
<h5>BLI</h5>
<ul>
<li>Michael Mosher updated the BLI Paragon 3 and 2 decoders</li>
</ul>
<h5>Digitrax</h5>
<ul>
<li>John McMasters updated the Digitrax Extended Series 6 v3.5</li>
</ul>
<h5>Doehler & Haas</h5>
<ul>
<li><a href="https://github.com/JMRI/JMRI/pull/97">Pierre Billon improved and
consolidated the D&H definitions</a></li>
<li>Pierre Billon updated the Doehler & Haas definitions,
including adding a new entry for the 1.06 version of the SH10A
</ul>
<h5>ESU</h5>
<p>Dave Heap made the following changes:</p>
<ul>
<li>Added the "Random Single Strobe" effect to Function Outputs.</li>
<li>Added the LokSound Select OEM.</li>
<li>Fixed the sense of the Adaptive Regulation Frequency bit.</li>
<li>Preliminary support for ESU LokSound Select L.</li>
<li>Corrected some maximum values and bitmasks on the
Function Outputs pane.</li>
<li>Various updates and corrections, including new Product IDs for correct decoder identification.</li>
</ul>
<h5>MERG</h5>
<ul>
<li>The MERG ACC5 definition has been converted to the
modern format of internal variables from the older
"ivariable" form.
</ul>
<h5>MGP</h5>
<ul>
<li>Anders Bostrom provided definitions for the <a href="http://mollehem.se">MGP</a>
LocoBridge,
Servo5, Panel and Signal 10 decoders. These use the LocoNet
VS2 protocol to configure the units over a LocoNet, not
over a programming track.
</li>
</ul>
<h5>MTH</h5>
<ul>
<li>Michael Mosher provided patch: 1069</li>
</ul>
<h5>NCE</h5>
<ul>
<li>Dave Heap corrected the range of CVs 3 & 4 for some decoders.</li>
</ul>
<h5>QSI</h5>
<ul>
<li>Some QSI decoder definitions have been converted to the
modern format of their internal variables from the older
"ivariable" form. The rest will be done early in the JMRI 4.3 release series.
<li>A problem with the "Max Bell" and "Bell Select"
variables in several QSI definitions was fixed.</li>
<li>Dave Heap made the following changes:<br>
<ul>
<li>Added a definition for the Eureka 50 Class.</li>
<li>Improved the definition for the Eureka R Class.</li>
<li>Added the ability to import CV values from Quantum CV Manager
(.qcv) files.</li>
<li>Factory Reset uses Paged Mode (more reliable with some command stations,
such as NCE Power Pro).</li>
<li>Factory Reset can be done with Programming on Main.</li>
<li>Corrected the range of CVs 3 & 4 for some decoders.</li>
</ul>
</li>
</ul>
<h5>RR-CirKits</h5>
<ul>
<li>The LNCP Basic definition has been converted to the
modern format of internal variables from the older
"ivariable" form.</li>
<li>Dick Bronson provided a definition for the RR-CirKits SwitchMan</li>
<li>The MotorMan decoder definition was updated.</li>
</ul>
<h5>SoundTraxx</h5>
<ul>
<li>Michael Mosher added the Econami range.</li>
<li>Dave Heap clarified the interaction between the Extended
and Legacy Function Map panes in the Econami range.</li>
<li>Updated the Econami Steam to use a separate SoundPane to warn about
the issue with the chuff and 'original' Econami decoders.
The value range now supports 0-255, but 'original' Econami decoders
will go silent if value is >127.
Soundtraxx will reprogram the decoder to allow the new range.</li>
<li>Michael Mosher updated the Soundtraxx MC decoders</li>
<li>Michael Mosher updated the Genesis caboose lighting decoder</li>
<li>Dave Heap corrected the range of CVs 3 & 4 for some decoders.</li>
</ul>
<h5>TCS</h5>
<ul>
<li>The "Global lighting option 1" on many TCS decoders has been fixed.</li>
<li>Michael Mosher provided patch: 1070 to update WOW diesel sound set 2</li>
<li>Peter Ulvestad corrected the tooltips in some of the TCS decoder definitions</li>
<li>Michael Mosher removed the non-existance CV139 from the non-sound TCS decoders</li>
</ul>
<h4>Operations</h4>
<ul>
<li>Improved train build report to first show which tracks in staging can service the train
being built.</li>
<li>Made some improvements to the spur window to show the current schedule status.</li>
<li>You can now copy a schedule, see under tools in the edit schedule window, or schedules
window.</li>
<li>The "Show Schedules by Car Type and Load" window now has the option
to show all loads.</li>
<li>You can now open all edit location windows at the same time. Previously you could only
open two edit location windows at once.</li>
<li>CSV switch lists now include hold cars.</li>
<li>CSV manifests how include hold cars for tracks that are only served
by the train being built.</li>
<li>New "Yardmaster by Track" window can be found under "Tools" in the
"Yardmaster" window. This window shows the work for a location listed by tracks.
It also shows the hold cars for each track.</li>
<li>Improved the train build when using aggressive mode and small move counts in a train's
route. Now there's a slight bias to pick up an extra car during the first
couple of passes.</li>
<li>Improved the "Change Train Departure Times" tool to also adjust departure times in a
train's route.</li>
<li>The "Edit Car" window now shows the blocking order for kernels.</li>
<li>Changed how the program deals with alternate tracks and cars with custom loads.
Previously if the program found an alternate track assigned to a spur, and all spurs
were full, it would hold the car at its current location until one of the spurs had
space for the car. Now there's a new option for a spur that is part of the load option
window for a spur. A checkbox labeled "Hold cars with custom loads when spurs are full"
now performs the same function as the alternate track did with regards to holding cars.
For more information, see the help and "Load Options" for a spur.</li>
<li>Make some improvement to the train build report. Now when selecting detailed or very
detailed "Router Detail Level", the program will show which spur / schedules are
ignored when generating custom loads out of staging.</li>
<li>Made some improvement to the train "Show Car Types Serviced" with regards to showing
better messages when selecting a car and there are track destination restrictions for
that car's track.</li>
<li>Made some improvements to the help with regards to schedules.</li>
<li>Fixed a bug where the train build reports were placed in a directory called
"operationsbuildstatus". This problem was introduced in version 4.1.1.
You can delete this directory if you've used any of the test versions.</li>
</ul>
<h4>OBlocks</h4>
<ul>
<li>Add feature for Tracker to follow trains into and through dark OBlocks.</li>
<li>Allow international locales to correctly specify lengths in
OBlock tables. (Matt Harris)</li>
</ul>
<h4>Preferences</h4>
<p></p>
<ul>
<li>Some preferences are now stored in properties files in the <code>preferences</code>
directory within the current profile. The file <code>preferences.properties</code>
contains settings that a common to all computers using that profile,
while the file (or files) named in the pattern
<code>jmri-<MAC address>-<profile-hash>.properties</code>
contain per-computer settings.</li>
<li>Web Server and JSON Server preferences are now stored in the above format.
Although the pre-JMRI 4.1 settings files for these servers are not removed,
changes to these services' settings made in JMRI 4.1 will not be available
to earlier versions of JMRI. These services' settings will only be migrated
to the new format by clicking Save in the Preferences window.</li>
<li>mDNS / Bonjour / ZeroConf network services advertisements can be
blocked on IPv4 or IPv6 addresses by editing the the per-computer
preferences file to include either or both of the following lines:
<ul>
<li><code>jmri-util-zeroconf.IPv4=false</code></li>
<li><code>jmri-util-zeroconf.IPv6=false</code></li>
</ul>
Valid values for these settings are <code>true</code> or <code>false</code>.
Note that this is an experimental feature.</li>
<li>Copying a Configuration Profile no longer throws an error. (Randall Wood)</li>
</ul>
<h4>Logix</h4>
<ul>
<li>Enhancement Request #574 implemented. Can use fractions of seconds for timing.</li>
<li>Add feature to set sensor/turnout delay times indirectly from memory.</li>
</ul>
<h4>Roster</h4>
<ul>
<li>Clarify if an entry will be deleted from the Roster or from a group in the context menu. (Randall Wood)</li>
<li>Allow a multiple selection of entries in the Roster or a group to be deleted. (Randall Wood)</li>
</ul>
<h4>Roster Speed Profile</h4>
<p>Improvements made to the UI.</p>
<ul>
<li>The starting and ending speed steps can be set for measuring a profile. Also the
increment for each profile step may be set</li>
<li>The speed profile will interpolate or extrapolate for omitted speed steps<li>
<li>The speed profile can be viewed in a table</li>
<li>There is an option to merge or replace the speed profile</li>
</ul>
<h4>Panel Editors</h4>
<ul>
<li>Fix backgrounds of text to stay transparent when rotated.</li>
<li>Fix false resizing of IndicatorTrackIcons</li>
<li>Fix spurious window names appearing under "Windows" menu</li>
<li><p>The code for handling Panel Editor / Control Panel Editor icons has changed
to better deal with rotating icons. This has changed how opaque vs transparent
icon backgrounds are handled.</p>
<p>The cause of these effects was the necessity to remove many setOpaque(true) calls
to Positionable objects. The reason is that when rotated with a color background
the object cannot be setOpaque(true). If opaque, color background will be the entire
bounding box, not a shape corresponding to the original item.
To display a rotated Positionable, the background, margins and border, if any,
are drawn with rotated and filled rectangles to simulate what is normally the
unrotated bounding rectangle and border.</p>
<p>The affected objects are PositionableLabels, SensorIcons (especially when
represented with text rather than icons) and MemoryIcons.
MemoryInputIcons, MemoryComboIcons and MemorySpinnerIcons are also affected,
due to the background, margin and border code they share with
PositionableLabel decendants.
(They can't be rotated due to having widgets that won't rotate)</p>
</li>
</ul>
<h4>Scripting</h4>
<ul>
<li>Support for running ECMAScript and JavaScript from external files has been added
in all cases except within Jynstruments.</li>
<li>Jython has been upgraded to version 2.7.0.</li>
<li>Any Java-compatible ScriptEngine can be included by including the ScriptEngine JA
file in the JMRI Classpath.</li>
<li>The decodeJmriFilename() function is no longer available by default.
Use the FileUtil.getExternalFilename() method instead.</li>
<li>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.</li>
<li>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.</li>
<li>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.</li>
<li>The "MakeOriginalDecoderPro.py" script has been corrected to work with the updated
scripting support introduced in <a href="jmri4.1.2.shtml">JMRI 4.1.2</a>.</li>
<li>The "AutoDispatcher2.py" script has been corrected to work with
the updated scripting support when the "jython.exec=true" setting
is set within the "python.properties" file.</li>
<li>Certain Python scripts are too large to be evaluated in Jython.
If a script fails with the <code>java.io.IOException: Mark
invalid</code> error, 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 to emulate the evaluation environment used when
jython.exec=false. (Randall Wood)</li>
<li>The user-defined scripts folder and the jython folder in the
JMRI installation are automatically appended to the python.path so
Jython scripts can directly import other jython scripts in those
locations. (Randall Wood)</li>
<li>Support for AppleScript has been added. On platforms other than OS X, this may send
the message
<code>ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found</code>
to the console, but this message can be safely ignored. (Randall Wood)</li>
<li>The jmri_bindings.py file is now available in the jython directory.</li>
</ul>
<h4>Miscellaneous</h4>
<p></p>
<ul>
<li>Improved the script editor (Panels -> Script Entry):
<ul>
<li>Now remembers the selected directory from operation to operation,
so you don't have to renavigate each time.
<li>Use the same file selector for Load and Store, so it's
easy to work in one directory.
<li>Use a proper Store dialog so you can e.g. change the
filename.
</ul>
</li>
<li>Include a python.properties for configuring the Jython environment.</li>
<li>Improve
<a href="http://jmri.org/help/en/html/doc/Technical/WebSite.shtml">instructions</a>
for making a local copy of the JMRI web site
and providing a local XML catalog.</li>
<li>Sonny Hansen has greatly improved the Danish translation.</li>
<li>The Multiple Decoder Programming tool is back to being available
in the DecoderPro tools menu. Also, you can add it as a button or
startup item in PanelPro and DecoderPro.</li>
<li>The Danish translations has been made more general. It was coded as
_da_DK, which is "Danish (Denmark)". That's been changed to _da, which
is generic "Danish", no matter where spoken. If you have local translation
files for Danish, this might conflict. Contact the JMRI list for help
with this. Contributed translations are always welcome!</li>
<li>The "Check XML File" option under the PanelPro Debug menu didn't need
to be a separate item, as it was already included in "Validate XML File".
It's been removed, please select the "Validate XML File" from now on.</li>
<li>You can now add "Validate XML File" as a custom button via the Start Up pane
in the Preferences.</li>
<li>A bug that caused panels not to be stored when empty AudioBuffers had been created
via a script has been fixed. (Matthew Harris)</li>
<li>Paul Bender updated the consist tool to sort the consist list numerically.</li>
<li>Paul Bender added restore button to the consist tool that requests the
command station re-create the consist.
<li>The configuration is now stored in multiple files within a directory named
<code>profile</code> inside a Configuration Profile instead of within the file
<code>ProfileConfig.xml</code>. PanelPro and DecoderPro both should migrate from
the old configuration to the new configuration seamlessly.
See <a href="https://github.com/JMRI/JMRI/issues/69#issuecomment-155385101">Issue #69</a>
for more details.</li>
<li>Improvements to the way TCP based network connections detect a disconnected server.</li>
<li>Update of the OperationsPro online Manual up to 3.11 and general readability (Egbert Broerse).</li>
<li>A script to disable or enable IPv4 and IPv6 support in zero configuration networking, named <code>zeroconf-preferences.js</code>, can be downloaded from <a href="https://raw.githubusercontent.com/JMRI/JMRI/master/jython/zeroconf-preferences.js">GitHub</a>. This may help some users having issues with the iPhone WiThrottle app. (Randall Wood)</li>
</ul>
<!--#include virtual="/Footer" -->
</div><!-- closes #mainContent-->
</div> <!-- closes #mBody-->
</body>
</html>