Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
Re: Roster Media - Images disappear in one profile - disappear but reappear when roster rebuilt in different profile
#rosterimage
¿ªÔÆÌåÓýOn Sat, 11 Jan 2025 Steve G wrote:
|
|
Re: Locomotive colors
#operationspro
On Sat, Jan 11, 2025 at 09:47 AM, Micheal wrote:
I tried to call up an older manifest within JMRI and they now print in all-black. The Pick Up and Set Out colors are gone. If you have an old Manifest that you want to print in color, simply press the "Save" button in the "Manifest Print Options" window and all of your old Manifests for built trains will get updated.? Older saved Manifest will print in black.
?
Dan |
|
Re: Roster Media - Images disappear in one profile - disappear but reappear when roster rebuilt in different profile
#rosterimage
Thanks. That makes sense; I see all the images in the dropbox roster directory. For the roster.xml file on dropbox it has ¡°imageFilePath="" for each locomotive. Do I change all those, individually, or is there a way to globally change the path? |
|
Re: Layout Editor questions
#layouteditor
Thanks Dave, Much appreciated Yves On Fri, Jan 10, 2025 at 8:58?AM Dave Sand via <ds=[email protected]> wrote:
|
|
Re: Locomotive colors
#operationspro
On Sat, Jan 11, 2025 at 09:47 AM, Micheal wrote:
?BN 1946 GP9 from Roundhouse 18? ? -? ? ?this line printed black on manifest Looking at your Manifest, I now see how you got the locomotive to print in black.? You eliminated the prefixes for both engine pulls and drops.? Yes, that would have printed in black in the older versions. |
|
Re: Locomotive colors
#operationspro
Micheal,
?
As far back as I can remember, both the locomotives and cars where printed in color.? Not sure how you got the locomotives to print in black.? Here's the results using 4.26, the oldest version I currently have on my PC.
?
|
|
Locomotive colors
#operationspro
Within one of the last handful of test releases of JMRI, my locomotives have turned color!
?
When I now preview or print a manifest, the listed locomotives had always been printed in black at both their Pick Up and Set Out location. However, now they are printed in the Pick Up and Set Out colors that are set within the program's settings. I also notice now that in the .txt files for manifests and switch lists that the Pick Up and Set Out colors are indicated in each Pick Up or Set Out line. Is this considered and update or feature to the program? If so, is there a way to toggle this locomotive color change back to black if preferred?
?
Example of an older version:
Scheduled work at Mandan, ND
<FONT color="magenta">Obtain Train Order from Dispatcher prior to Departure.</FONT> ?BN 1946 GP9 from Roundhouse 18? ? -? ? ?this line printed black on manifest ?BN 1947 GP9 from Roundhouse 18? ? ?-? ? this line printed black on manifest ?[ ] Pull SP&S 13492 Boxcar 41' MTY from 1 Track? ? -? ? this line printed red on manifest ?[ ] Pull GN 5111 Boxcar 41' MTY from 1 Track? ? -? ? this line printed red on manifest ?[ ] Pull CB&Q 83416 Gondola 54' Shafts from 7 Track? ? -? ? this line printed red on manifest ?[ ] Pull GN 2530 Boxcar 41' MTY from 1 Track? ? -? ? this line printed red on manifest. ?
Example of a newer version:
Scheduled work at Mandan, ND
Coordinate all movements with Mandan Yardmaster. <FONT color="red"> BN 4081 RS3 from Roundhouse 23</FONT> <FONT color="red"> [ ] Pull CB&Q 83453 Gondola 54' MTY from Welk Steel</FONT> <FONT color="red"> [ ] Pull CP 85664 Boxcar 50' Newsprint from 5 Track</FONT> <FONT color="red"> [ ] Pull BN 449053 CvdHpr 54' MTY from 1 Track</FONT> <FONT color="red"> [ ] Pull BN 11255 Caboose 36' MTY from Cab Alley</FONT> ?
I tried to call up an older manifest within JMRI and they now print in all-black. The Pick Up and Set Out colors are gone.
?
Micheal Farley
Bismarck, ND
www.facebook.com/yellowstonedivision
|
|
Re: Control Panel Editor Icon Scaling
#controlpaneleditor
...and come to think if it, I experienced some of those inconsistencies in the past but brushed it off... it all makes sense now, thanks again. |
|
Re: Control Panel Editor Icon Scaling
#controlpaneleditor
Ok cool, Bobl! Thank you for the improvement and quick reply! Sorry I didn't see that in the release notes. It made me motivated to upgrade my windows7 box so I can get to java17. |
|
Re: Roster Media - Images disappear in one profile - disappear but reappear when roster rebuilt in different profile
#rosterimage
If you look in the roster.xml file you will see the filenames being used
e.g. imageFilePath="home:JMRI-Files/JMRI-Roster/roster/CNR1026.jpg"
All our files have the same relative path from the users home directory.
?
Steve G. |
|
Re: Roster Media - Images disappear in one profile - disappear but reappear when roster rebuilt in different profile
#rosterimage
Bob
You likely have the images in different places for each pc. They need to be stored in a relative path to the files section or roster. So they appear as roster:: or files::.
Steve G.
? |
|
Re: Roster Media - Images disappear in one profile - disappear but reappear when roster rebuilt in different profile
#rosterimage
Bob, Sometimes I do run both at the same time, but not normally. While trying to resolve this, I have tried it while running both and while running just one; no difference in the behavior of the roster media. So far, I have: A. uninstalled Java 19 and Java 21, respectively, and installed Java 17 on both computers. No change in behavior. (May go down to Java 11 later.), B. disabled firewalls, antivirus etc, on Windows 11 computer with no resulting change, and C. copied existing profile on Windows 11 and renamed it, edited it somewhat, and retried; no change. I plan to try creating a new profile on the Windows 11 computer and if that doesn¡¯t work I plan to copy the Windows 10 profile to Windows 11 computer. Bob |
|
Re: Control Panel Editor Icon Scaling
#controlpaneleditor
This is a change in release 5.10. From the release note:
? The "Scale" operation on icons has been changed to a relative scaling from the current size. For example, if you've scaled an icon by 150% already, and request a rescaling by 200%, the icon will end up at 300%. Previously, this would work inconsistently. So for your example you started at 80%, scaled that by 60% and ended up at .8*.6 = 48%. To make things larger, use a number over 100%. The change was made because the prior approach was working inconsistently. In some cases it was an absolute scaling: Enter the ratio of the original size to what you want. But in others it was a relative scaling: Enter the ratio of the _previous_ size to what you want. That was confusing, and There Were Complaints. So the logic was changed to be (more) consistent, and the language around the scaling action was updated to (hopefully) be clearer. Labelling this is a little tough, because ¡°scale¡± can be both a noun and a verb: Is the entry box showing the desired final _scale_, or the amount by which to _scale_ the existing object? If you find a place where that¡¯s still not clear, let me know so I can improve it. (The Scale operation happens in so many places that some might have been missed when cleaning this up) Bob On Jan 10, 2025, at 7:06?PM, Vinny DeRobertis via groups.io <vinny.derobertis@...> wrote:¡ª Bob Jacobsen rgj1927@... |
|
Re: Roster Media - Images disappear in one profile - disappear but reappear when roster rebuilt in different profile
#rosterimage
Are you running JMRI on the two computers at the same time?
Bob On Jan 10, 2025, at 6:59?PM, RBD via groups.io <rdunham@...> wrote:¡ª Bob Jacobsen rgj1927@... |
|
Eric, You have added new variables with ONESENSOR and DIRECT. When a xml data file is loaded, the turnouts will have an UNKNOWN state. ?For turnouts using MONITORING, JMRI will request the state from the NCE command station. ?For turnouts using ONESENSOR, the AIU sensor state will be used for the turnout. ?For DIRECT nothing happens. This is what I see using the NCE Simulator. ?I don't have NCE equipment so I cannot test a real connection. After starting a PowerPro NCE command station, the accessory decoder table has 2048 bits set to zero. ?Zero is turnout THROWN, one is turnout CLOSED. ?As the command station sees accessory decoder messages, the bits are changed based on the accessory command. ?External changes using push buttons are not detected. ?JMRI checks for changes to the bit map about 4 times a second. The first click on the DIRECT turnout changes the state from UNKNOWN to CLOSED. Dave Sand ----- Original message ----- From: "Eric Troup via groups.io" <etroup=[email protected]> Subject: Re: [jmriusers] NCE Accessory Event Monitoring and possibly CS-105 #nce Date: Friday, January 10, 2025 7:16 PM Dave, ? Setting the conditions of the test as you state if: 1. turnouts configured in Monitoring or One Sensor Mode, the state in the turnout xml table tends to match the physical state - or at least matches the state when system was turned off. 2. turnouts configured in Direct Mode tend to show up as Thrown regardless of their true physical state. Clicking on the turnout icon changes the state to the actual state. Clicking a second time changes the state.? ? I made a video of the test under condition two but this system says the file is too big to send as an attachment. |
|
Re: Exporting locomotive roster
#roster
Mark
toggle quoted message
Show quoted text
On Jan 10, 2025, at 10:04?PM, miktrain via groups.io <miktrain@...> wrote:
|
|
Re: Exporting locomotive roster
#roster
Mark, Read this: It's the only available way that I have found. On Fri, Jan 10, 2025 at 10:47?AM Mark via <mrfernald=[email protected]> wrote:
--
John Griffin Model Railroading Topics |
|
Dave,
?
Setting the conditions of the test as you state if:
1. turnouts configured in Monitoring or One Sensor Mode, the state in the turnout xml table tends to match the physical state - or at least matches the state when system was turned off.
2. turnouts configured in Direct Mode tend to show up as Thrown regardless of their true physical state. Clicking on the turnout icon changes the state to the actual state. Clicking a second time changes the state.?
?
I made a video of the test under condition two but this system says the file is too big to send as an attachment. |