¿ªÔÆÌåÓý

  1. Jmriusers
  2. Topics

Edit dialog boxes do not open with full width

 

Now that I'm running with version 5.10 and Azul 17 LTS, I pulled over a profile from my previous system to continue working on it and I noticed when when I click the Edit button on various table items (e.g., Sensors, Blocks, Turnouts...looks like all of them), I get an edit window popping up that appears to be the correct height but has almost no width. For example, here is a section of my Blocks table:
?
?
.... and if I click on the Edit button in the highlighted row (although it could be any row), I initially get:
?
?
?
Then, once I drag the right box side to the right, I get:
?
?
Which looks about right.
?
I noticed a similar problem on startup when choosing a new profile:
?
?
?
?
The difference with this one is that once I stretch it and and close PanelPro, I get the full dialog next time I open it. With the table element editors shown above, it happens every time.
?
One last observation - if I create a new profile from the startup page (where I can either wait x seconds to take the default, or choose another, or create a new profile), and then select that new profile to start, I again get a skinny window that appears to be the right height but has a similarly narrow width:
?
?
?
With this one, once again, once I stretch it out it appears to be good going forward. In fact, I can just close JMRI and reopen it and I get a normal size window.
?
If this were a web page, I would swear I have a bad or missing .css file. Looks simpler in this case, though. Might be that all of these skinny windows are initially the same width....like JMRI is missing a parameter somewhere that describes my monitor sizes? Maybe I accidentally corrupted something in the process of reinstalling Java and JMRI 5.10 when dealing with my previous problem?
?
Vince
 

Vince,

How did you transfer the JMRI data from the previous system? ?What was the previous system? ?Hardware, OS, JMRI version, etc.

Are there any errors in the system console (Help -> System Console)?

Go to "Help -> Context", click on the "Copy to clipboard" button and paste into a reply.

Dave Sand


----- Original message -----
From: "Vince Guarna via groups.io" <vince=[email protected]>
Subject: [jmriusers] Edit dialog boxes do not open with full width
Date: Monday, May 19, 2025 9:55 PM

Now that I'm running with version 5.10 and Azul 17 LTS, I pulled over a profile from my previous system to continue working on it and I noticed when when I click the Edit button on various table items (e.g., Sensors, Blocks, Turnouts...looks like all of them), I get an edit window popping up that appears to be the correct height but has almost no width. For example, here is a section of my Blocks table:
?

?
.... and if I click on the Edit button in the highlighted row (although it could be any row), I initially get:
?

?
?
Then, once I drag the right box side to the right, I get:
?

?
Which looks about right.
?
I noticed a similar problem on startup when choosing a new profile:
?

?
?
?
The difference with this one is that once I stretch it and and close PanelPro, I get the full dialog next time I open it. With the table element editors shown above, it happens every time.
?
One last observation - if I create a new profile from the startup page (where I can either wait x seconds to take the default, or choose another, or create a new profile), and then select that new profile to start, I again get a skinny window that appears to be the right height but has a similarly narrow width:
?
?

?
With this one, once again, once I stretch it out it appears to be good going forward. In fact, I can just close JMRI and reopen it and I get a normal size window.
?
If this were a web page, I would swear I have a bad or missing .css file. Looks simpler in this case, though. Might be that all of these skinny windows are initially the same width....like JMRI is missing a parameter somewhere that describes my monitor sizes? Maybe I accidentally corrupted something in the process of reinstalling Java and JMRI 5.10 when dealing with my previous problem?
?
Vince
 

No errors in the log (didn't even know I could get the log when not running from a shell....thx).
?
Previous system was (and still is) an old Intel iMac running 5.10 and Java 11. Ventura OS.
?
New system is M4 Mac Studio running Sequoia (and 5.10 and Java 17 as you know from my previous post).
?
I just copied over the xxx.jmri folder over from the old system to the new system. Things generally seemed to look OK (layout panels were correct, tables looked right, etc). But, I did change the default location of the .jmri folders (as I did with the old system).
?
Your questions have me thinking about moving the default config folder location. Even though it worked before, who knows what other little things I might have done along the way that might have had an impact.
?
For a better-controlled test environment for the A/B comparison I think I will delete and re-install JMRI and try again using just the default My_JMRI_Railroad profile for testing. I am assuming that deleting /Applications/JMRI and ~/Library/Preferences/JMRI will get me back to a clean install state.
?
Vince
 

OK, clean start.
?
  1. Wiped out /Applications/JMRI and /Users/Vince/Library/Preferences/JMRI.
  2. Re-installed 5.10
  3. Started JMRI for the first time
  4. It creates My_JMRI_Railroad and opens the skinny settings window.
  5. I stretch the settings window
  6. Added a LocoNet simulator connection
  7. Allow it to restart JMRI.
  8. Open the settings window - it looks fine (it remembered the size I set it to)
  9. Go to Tools -> Tables -> Turnouts
  10. Add a LocoNet turnout LT333
  11. Click the Edit button on the line for that turnout in the table (it's the only line, of course).
  12. It's a skinny edit window. I stretch it out until the layout is correct.
  13. Added a comment
  14. Clicked Apply and OK.
  15. The table now reflects the comment I added (good)
  16. Click edit again and get the skinny window again (it did not remember the size I stretched it to)
  17. Open the console log - it's a skinny window
  18. Stretch the window out far enough for no line breaks.
  19. Close the window.
  20. Reopen the console window - it remembered the size.
  21. Here's the log (no errors):
?
This should all have been done with a fresh JMRI installation. No new folders, no extra profiles. Most non-UI things seem to work. For fun, I opened the Monitor LocoNet window. It first appears as a skinny window but I stretched it and it retains its size after closing and re-opening and also quitting and restarting JMRI. Pushed the State button on the table a few times and the right message appear in the monitor window, FWIW.
?
The problem is so consistent - seems like it's one of those "simple once you know what it is" things. But I can't think of anything else to look at or try.
?
Vince
 

Vince,

For future reference, use the "Copy to clipboard" button to get the system console text. ?Screenshots don't zoom well and the text cannot be copied.

Since you are running a Mac Studio, that means you have an external monitor. ?What is it? ?Also, go to "Help -> Context". ?Use the "Copy to clipboard" button and paste the content. ?That should tell us what the display looks like to Java.

Make note of the "storage identify" line. ?The user-interface.xml file is located within that directory which is in the profile directory at the user files location. ?That file contains a number of GUI settings, including window location and sizes. ?

Dave Sand


----- Original message -----
From: "Vince Guarna via groups.io" <vince=[email protected]>
Subject: Re: [jmriusers] Edit dialog boxes do not open with full width
Date: Tuesday, May 20, 2025 9:05 AM

OK, clean start.
?
  1. Wiped out /Applications/JMRI and /Users/Vince/Library/Preferences/JMRI.
  2. Re-installed 5.10
  3. Started JMRI for the first time
  4. It creates My_JMRI_Railroad and opens the skinny settings window.
  5. I stretch the settings window
  6. Added a LocoNet simulator connection
  7. Allow it to restart JMRI.
  8. Open the settings window - it looks fine (it remembered the size I set it to)
  9. Go to Tools -> Tables -> Turnouts
  10. Add a LocoNet turnout LT333
  11. Click the Edit button on the line for that turnout in the table (it's the only line, of course).
  12. It's a skinny edit window. I stretch it out until the layout is correct.
  13. Added a comment
  14. Clicked Apply and OK.
  15. The table now reflects the comment I added (good)
  16. Click edit again and get the skinny window again (it did not remember the size I stretched it to)
  17. Open the console log - it's a skinny window
  18. Stretch the window out far enough for no line breaks.
  19. Close the window.
  20. Reopen the console window - it remembered the size.
  21. Here's the log (no errors):

?
This should all have been done with a fresh JMRI installation. No new folders, no extra profiles. Most non-UI things seem to work. For fun, I opened the Monitor LocoNet window. It first appears as a skinny window but I stretched it and it retains its size after closing and re-opening and also quitting and restarting JMRI. Pushed the State button on the table a few times and the right message appear in the monitor window, FWIW.
?
The problem is so consistent - seems like it's one of those "simple once you know what it is" things. But I can't think of anything else to look at or try.
?
Vince
 

Sorry about the image pasting for the log....rookie mistake.
?
I have two monitors. My main display is the Apple 27" 5K display (5120x2880) and the other is an old 27" Thunderbolt display (2560x1440).
?
It's interesting that JMRI was opening on my secondary screen (lower res). And, I can see in the context file that its resolution is reflected there. I did another quick experiment by moving the startup JMRI dialog to my main screen and close/re-opened JMRI. The startup dialog was then on the main screen. No change in behaviors, tho.
?
By the way, my older machine is one of the old Intel iMacs that also has a 5K screen. I used this same Thunderbolt monitor as the secondary screen. JMRI 5.10 worked fine there. FWIW. I'm going to do a diff on the two context files to see if there's anything interesting to look at.
?
Here is the content of the Context window (I XXX'ed out local network specifics figuring they were not important):
?

JMRI Version: 5.10+Rca461bd266 ??
JMRI configuration file name: null ? (from org.jmri.apps.Apps.configFilename system property)
JMRI main window name: LocoNet Simulator ??
JMRI Application: PanelPro ??
Connection 0: Digitrax connected via LocoNet Simulator on (none) Disabled false ??
Available Communication Ports:
?Found 4 serial ports
?Port: cu.debug-console
?Port: tty.debug-console
?Port: cu.Bluetooth-Incoming-Port
?Port: tty.Bluetooth-Incoming-Port
Active profile: My JMRI Railroad ??
Profile location: /Users/vince/Library/Preferences/JMRI/My_JMRI_Railroad.jmri ??
Profile ID: My_JMRI_Railroad.3f232d79 ??
JMRI Network ID: jmri-1C1DD3D6BA2F-3f232d79
JMRI Storage ID: 659c4cb1-9b31-46e2-8f8f-0f98b2459238
Preferences directory: /Users/vince/Library/Preferences/JMRI/My_JMRI_Railroad.jmri/ ??
Program directory: /Applications/JMRI ??
Roster index location: /Users/vince/Library/Preferences/JMRI/My_JMRI_Railroad.jmri/roster.xml ??
Current panel file: [none] ??
Locale: en
Audio factory type: [not initialised] ??
java.version: 17.0.15 ??
java.vendor: Azul Systems, Inc. ??
java.home: /Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home ??
java.vm.version: 17.0.15+6-LTS ??
java.vm.vendor: Azul Systems, Inc. ??
java.vm.name: OpenJDK 64-Bit Server VM ??
java.specification.version: 17 ??
java.specification.vendor: Oracle Corporation ??
java.specification.name: Java Platform API Specification ??
java.class.version: 61.0 ??
java.class.path: .:classes:target/classes:jmri.jar:lib/JavaVersionCheckWindow.jar:lib/apiguardian-api-1.1.0.jar:lib/batik-anim-1.14.jar:lib/batik-awt-util-1.14.jar:lib/batik-bridge-1.14.jar:lib/batik-constants-1.14.jar:lib/batik-css-1.14.jar:lib/batik-dom-1.14.jar:lib/batik-ext-1.14.jar:lib/batik-gvt-1.14.jar:lib/batik-i18n-1.14.jar:lib/batik-js-1.8.jar:lib/batik-parser-1.14.jar:lib/batik-script-1.14.jar:lib/batik-shared-resources-1.14.jar:lib/batik-svg-dom-1.14.jar:lib/batik-svggen-1.14.jar:lib/batik-transcoder-1.17.jar:lib/batik-util-1.14.jar:lib/batik-xml-1.14.jar:lib/beansbinding-1.2.1.jar:lib/bidibwizard-common-2.0.18.jar:lib/bidibwizard-model-2.0.18.jar:lib/bidibwizard-simulation-2.0.18.jar:lib/bluecove-2.1.1-SNAPSHOT.jar:lib/bluecove-bluez-2.1.1-SNAPSHOT.jar:lib/bluecove-gpl-2.1.1-SNAPSHOT.jar:lib/commons-collections4-4.4.jar:lib/commons-compress-1.18.jar:lib/commons-csv-1.9.0.jar:lib/commons-io-2.11.0.jar:lib/commons-lang3-3.7.jar:lib/commons-logging-1.2.jar:lib/commons-net-3.9.0.jar:lib/commons-text-1.2.jar:lib/eventbus-1.4.jar:lib/gluegen-rt.jar:lib/hid4java-0.5.0.jar:lib/jSerialComm-2.10.4.jar:lib/jackson-annotations-2.13.4.jar:lib/jackson-core-2.13.4.jar:lib/jackson-databind-2.13.4.2.jar:lib/javax.activation-api-1.2.0.jar:lib/javax.servlet-api-3.1.0.jar:lib/jaxb-api-2.3.1.jar:lib/jaxb-core-2.3.0.1.jar:lib/jaxb-impl-2.3.2.jar:lib/jbidibc-core-2.0.18.jar:lib/jbidibc-jserialcomm-2.0.18.jar:lib/jbidibc-messages-2.0.18.jar:lib/jbidibc-net-serial-over-tcp-2.0.18.jar:lib/jbidibc-serial-2.0.18.jar:lib/jbidibc-simulation-2.0.18.jar:lib/jdom2-2.0.6.jar:lib/jetty-http-9.4.28.v20200408.jar:lib/jetty-io-9.4.28.v20200408.jar:lib/jetty-security-9.4.28.v20200408.jar:lib/jetty-server-9.4.28.v20200408.jar:lib/jetty-servlet-9.4.28.v20200408.jar:lib/jetty-util-9.4.28.v20200408.jar:lib/jgoodies-binding-2.13.0.jar:lib/jgoodies-common-1.8.1.jar:lib/jhall.jar:lib/jinput-2.0.9-natives-all.jar:lib/jinput-2.0.9.jar:lib/jinputvalidator-0.8.0.jar:lib/jlfgr-1_0.jar:lib/jmdns-3.5.5.jar:lib/jmri.script.jsr223graalpython.jar:lib/jna-5.13.0.jar:lib/jna-platform-5.13.0.jar:lib/joal.jar:lib/json-schema-validator-1.0.28.jar:lib/jsoup-1.15.3.jar:lib/jsplitbutton-1.3.1.jar:lib/jul-to-slf4j-2.0.7.jar:lib/jython-standalone-2.7.4.jar:lib/libusb4java-1.3.0-darwin-aarch64.jar:lib/libusb4java-1.3.0-darwin-x86-64.jar:lib/libusb4java-1.3.0-linux-aarch64.jar:lib/libusb4java-1.3.0-linux-arm.jar:lib/libusb4java-1.3.0-linux-x86-64.jar:lib/libusb4java-1.3.0-linux-x86.jar:lib/libusb4java-1.3.0-win32-x86-64.jar:lib/libusb4java-1.3.0-win32-x86.jar:lib/log4j-api-2.20.0.jar:lib/log4j-core-2.20.0.jar:lib/log4j-slf4j2-impl-2.20.0.jar:lib/mailapi.jar:lib/openlcb.jar:lib/org-openide-util-lookup-RELEASE150.jar:lib/org.eclipse.paho.client.mqttv3-1.2.5.jar:lib/pi4j-core-1.2.jar:lib/purejavacomm-1.0.5.jar:lib/slf4j-api-2.0.7.jar:lib/thumbnailator-0.4.8.jar:lib/usb-api-1.0.2.jar:lib/usb4java-1.3.0.jar:lib/usb4java-javax-1.3.0.jar:lib/vecmath-1.5.2.jar:lib/websocket-api-9.4.28.v20200408.jar:lib/websocket-client-9.4.28.v20200408.jar:lib/websocket-common-9.4.28.v20200408.jar:lib/websocket-server-9.4.28.v20200408.jar:lib/websocket-servlet-9.4.28.v20200408.jar:lib/xAPlib.jar:lib/xbee-java-library-1.3.1.jar:lib/xercesImpl-2.12.2.jar:lib/xml-apis-ext-1.3.04.jar:lib/xmlgraphics-commons-2.6.jar ??
java.library.path: .:lib/macosx:lib ??
java.compiler: null ??
java.ext.dirs: null ??
file.encoding: UTF-8 ??
os.name: Mac OS X ??
os.arch: aarch64 ??
os.version: 15.5 ??
python.home: null ??
python.path: null ??
python.cachedir: null ??
python.cachedir.skip: null ??
python.startup: null ??
user.name: vince ??
user.home: /Users/vince ??
user.dir: /Applications/JMRI ??
user.country: US ??
user.language: en ??
user.timezone: America/Chicago ??
jmri.log.path: /Users/vince/Library/Preferences/JMRI/log/ ??
FileSystemView#getDefaultDirectory(): /Users/vince
FileSystemView#getHomeDirectory(): /Users/vince
Default JFileChooser(): /Users/vince
Screen size h:1440, w:2560 Inset t:0, b:0; l:0, r:0
Screen resolution: 108
Environment max bounds: java.awt.Rectangle[x=0,y=0,width=2560,height=1440]
Device: Display 3 bounds = java.awt.Rectangle[x=-2560,y=0,width=2560,height=1440]
Device: Display 3 insets = java.awt.Insets[top=0,left=0,bottom=0,right=0]
Device: Display 5 bounds = java.awt.Rectangle[x=0,y=0,width=2560,height=1440]
Device: Display 5 insets = java.awt.Insets[top=0,left=0,bottom=0,right=0]
JmriInsets t:0, b:0; l:0, r:0
Look and Feel: Mac OS X
Network Interface: ipsec0
?Long Name: ipsec0
?Host Name: XXX
?IP address: XXX
Network Interface: en1
?Long Name: en1
?Host Name: XXX
?IP address: XXX
Network Interface: en0
?Long Name: en0
?Host Name: XXX
?IP address: XXX
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
?
 

Vince,

The context looks ok. ?

You might try using a single monitor as a test.

It appears that you have the macOS menu bar hidden. ?That should not make a difference.

Dave Sand


----- Original message -----
From: "Vince Guarna via groups.io" <vince=[email protected]>
Subject: Re: [jmriusers] Edit dialog boxes do not open with full width
Date: Tuesday, May 20, 2025 10:10 AM

Sorry about the image pasting for the log....rookie mistake.
?
I have two monitors. My main display is the Apple 27" 5K display (5120x2880) and the other is an old 27" Thunderbolt display (2560x1440).
?
It's interesting that JMRI was opening on my secondary screen (lower res). And, I can see in the context file that its resolution is reflected there. I did another quick experiment by moving the startup JMRI dialog to my main screen and close/re-opened JMRI. The startup dialog was then on the main screen. No change in behaviors, tho.
?
By the way, my older machine is one of the old Intel iMacs that also has a 5K screen. I used this same Thunderbolt monitor as the secondary screen. JMRI 5.10 worked fine there. FWIW. I'm going to do a diff on the two context files to see if there's anything interesting to look at.
?
Here is the content of the Context window (I XXX'ed out local network specifics figuring they were not important):
?

JMRI Version: 5.10+Rca461bd266 ??
JMRI configuration file name: null ? (from org.jmri.apps.Apps.configFilename system property)
JMRI main window name: LocoNet Simulator ??
JMRI Application: PanelPro ??
Connection 0: Digitrax connected via LocoNet Simulator on (none) Disabled false ??
Available Communication Ports:
?Found 4 serial ports
?Port: cu.debug-console
?Port: tty.debug-console
?Port: cu.Bluetooth-Incoming-Port
?Port: tty.Bluetooth-Incoming-Port
Active profile: My JMRI Railroad ??
Profile location: /Users/vince/Library/Preferences/JMRI/My_JMRI_Railroad.jmri ??
Profile ID: My_JMRI_Railroad.3f232d79 ??
JMRI Network ID: jmri-1C1DD3D6BA2F-3f232d79
JMRI Storage ID: 659c4cb1-9b31-46e2-8f8f-0f98b2459238
Preferences directory: /Users/vince/Library/Preferences/JMRI/My_JMRI_Railroad.jmri/ ??
Program directory: /Applications/JMRI ??
Roster index location: /Users/vince/Library/Preferences/JMRI/My_JMRI_Railroad.jmri/roster.xml ??
Current panel file: [none] ??
Locale: en
Audio factory type: [not initialised] ??
java.version: 17.0.15 ??
java.vendor: Azul Systems, Inc. ??
java.home: /Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home ??
java.vm.version: 17.0.15+6-LTS ??
java.vm.vendor: Azul Systems, Inc. ??
java.vm.name: OpenJDK 64-Bit Server VM ??
java.specification.version: 17 ??
java.specification.vendor: Oracle Corporation ??
java.specification.name: Java Platform API Specification ??
java.class.version: 61.0 ??
java.class.path: .:classes:target/classes:jmri.jar:lib/JavaVersionCheckWindow.jar:lib/apiguardian-api-1.1.0.jar:lib/batik-anim-1.14.jar:lib/batik-awt-util-1.14.jar:lib/batik-bridge-1.14.jar:lib/batik-constants-1.14.jar:lib/batik-css-1.14.jar:lib/batik-dom-1.14.jar:lib/batik-ext-1.14.jar:lib/batik-gvt-1.14.jar:lib/batik-i18n-1.14.jar:lib/batik-js-1.8.jar:lib/batik-parser-1.14.jar:lib/batik-script-1.14.jar:lib/batik-shared-resources-1.14.jar:lib/batik-svg-dom-1.14.jar:lib/batik-svggen-1.14.jar:lib/batik-transcoder-1.17.jar:lib/batik-util-1.14.jar:lib/batik-xml-1.14.jar:lib/beansbinding-1.2.1.jar:lib/bidibwizard-common-2.0.18.jar:lib/bidibwizard-model-2.0.18.jar:lib/bidibwizard-simulation-2.0.18.jar:lib/bluecove-2.1.1-SNAPSHOT.jar:lib/bluecove-bluez-2.1.1-SNAPSHOT.jar:lib/bluecove-gpl-2.1.1-SNAPSHOT.jar:lib/commons-collections4-4.4.jar:lib/commons-compress-1.18.jar:lib/commons-csv-1.9.0.jar:lib/commons-io-2.11.0.jar:lib/commons-lang3-3.7.jar:lib/commons-logging-1.2.jar:lib/commons-net-3.9.0.jar:lib/commons-text-1.2.jar:lib/eventbus-1.4.jar:lib/gluegen-rt.jar:lib/hid4java-0.5.0.jar:lib/jSerialComm-2.10.4.jar:lib/jackson-annotations-2.13.4.jar:lib/jackson-core-2.13.4.jar:lib/jackson-databind-2.13.4.2.jar:lib/javax.activation-api-1.2.0.jar:lib/javax.servlet-api-3.1.0.jar:lib/jaxb-api-2.3.1.jar:lib/jaxb-core-2.3.0.1.jar:lib/jaxb-impl-2.3.2.jar:lib/jbidibc-core-2.0.18.jar:lib/jbidibc-jserialcomm-2.0.18.jar:lib/jbidibc-messages-2.0.18.jar:lib/jbidibc-net-serial-over-tcp-2.0.18.jar:lib/jbidibc-serial-2.0.18.jar:lib/jbidibc-simulation-2.0.18.jar:lib/jdom2-2.0.6.jar:lib/jetty-http-9.4.28.v20200408.jar:lib/jetty-io-9.4.28.v20200408.jar:lib/jetty-security-9.4.28.v20200408.jar:lib/jetty-server-9.4.28.v20200408.jar:lib/jetty-servlet-9.4.28.v20200408.jar:lib/jetty-util-9.4.28.v20200408.jar:lib/jgoodies-binding-2.13.0.jar:lib/jgoodies-common-1.8.1.jar:lib/jhall.jar:lib/jinput-2.0.9-natives-all.jar:lib/jinput-2.0.9.jar:lib/jinputvalidator-0.8.0.jar:lib/jlfgr-1_0.jar:lib/jmdns-3.5.5.jar:lib/jmri.script.jsr223graalpython.jar:lib/jna-5.13.0.jar:lib/jna-platform-5.13.0.jar:lib/joal.jar:lib/json-schema-validator-1.0.28.jar:lib/jsoup-1.15.3.jar:lib/jsplitbutton-1.3.1.jar:lib/jul-to-slf4j-2.0.7.jar:lib/jython-standalone-2.7.4.jar:lib/libusb4java-1.3.0-darwin-aarch64.jar:lib/libusb4java-1.3.0-darwin-x86-64.jar:lib/libusb4java-1.3.0-linux-aarch64.jar:lib/libusb4java-1.3.0-linux-arm.jar:lib/libusb4java-1.3.0-linux-x86-64.jar:lib/libusb4java-1.3.0-linux-x86.jar:lib/libusb4java-1.3.0-win32-x86-64.jar:lib/libusb4java-1.3.0-win32-x86.jar:lib/log4j-api-2.20.0.jar:lib/log4j-core-2.20.0.jar:lib/log4j-slf4j2-impl-2.20.0.jar:lib/mailapi.jar:lib/openlcb.jar:lib/org-openide-util-lookup-RELEASE150.jar:lib/org.eclipse.paho.client.mqttv3-1.2.5.jar:lib/pi4j-core-1.2.jar:lib/purejavacomm-1.0.5.jar:lib/slf4j-api-2.0.7.jar:lib/thumbnailator-0.4.8.jar:lib/usb-api-1.0.2.jar:lib/usb4java-1.3.0.jar:lib/usb4java-javax-1.3.0.jar:lib/vecmath-1.5.2.jar:lib/websocket-api-9.4.28.v20200408.jar:lib/websocket-client-9.4.28.v20200408.jar:lib/websocket-common-9.4.28.v20200408.jar:lib/websocket-server-9.4.28.v20200408.jar:lib/websocket-servlet-9.4.28.v20200408.jar:lib/xAPlib.jar:lib/xbee-java-library-1.3.1.jar:lib/xercesImpl-2.12.2.jar:lib/xml-apis-ext-1.3.04.jar:lib/xmlgraphics-commons-2.6.jar ??
java.library.path: .:lib/macosx:lib ??
java.compiler: null ??
java.ext.dirs: null ??
file.encoding: UTF-8 ??
os.name: Mac OS X ??
os.arch: aarch64 ??
os.version: 15.5 ??
python.home: null ??
python.path: null ??
python.cachedir: null ??
python.cachedir.skip: null ??
python.startup: null ??
user.name: vince ??
user.home: /Users/vince ??
user.dir: /Applications/JMRI ??
user.country: US ??
user.language: en ??
user.timezone: America/Chicago ??
jmri.log.path: /Users/vince/Library/Preferences/JMRI/log/ ??
FileSystemView#getDefaultDirectory(): /Users/vince
FileSystemView#getHomeDirectory(): /Users/vince
Default JFileChooser(): /Users/vince
Screen size h:1440, w:2560 Inset t:0, b:0; l:0, r:0
Screen resolution: 108
Environment max bounds: java.awt.Rectangle[x=0,y=0,width=2560,height=1440]
Device: Display 3 bounds = java.awt.Rectangle[x=-2560,y=0,width=2560,height=1440]
Device: Display 3 insets = java.awt.Insets[top=0,left=0,bottom=0,right=0]
Device: Display 5 bounds = java.awt.Rectangle[x=0,y=0,width=2560,height=1440]
Device: Display 5 insets = java.awt.Insets[top=0,left=0,bottom=0,right=0]
JmriInsets t:0, b:0; l:0, r:0
Look and Feel: Mac OS X
Network Interface: ipsec0
?Long Name: ipsec0
?Host Name: XXX
?IP address: XXX
Network Interface: en1
?Long Name: en1
?Host Name: XXX
?IP address: XXX
Network Interface: en0
?Long Name: en0
?Host Name: XXX
?IP address: XXX
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
ZeroConfService host: jmri-1c1dd3d6ba2f-3f232d79 running 0 service(s)
?
 

Cosmic -- I had just had the same thought when your email came in. I unplugged the Thunderbolt and, sure enough, the turnout edit dialog appears in full size!
?
This is partially good news...but I frequently have many tables open... as well as two full screen layout panels. Very crowded. I would also hate to have to unplug and replug a monitor every time I go into and out of JMRI.
?
Is there something I can look at to see what is different in the UI with one vs two monitors?
?
Also, I don't suppose it's relevant, but the older (working) machine runs with Adoptium version of Java 11.
?
Vince
 

Breaking News....I plugged the second monitor in again and now all seems to be working.
?
I'll try adding a new profile or two to see if the luck holds....
?
Vince
 

Following up: I created a new config profile with both monitors plugged in. I'm leaving everything in the default location (~/Library/Preferences/JMRI/<profile>.jmri)? now even though I had no problem with that in the past. I set the new profile as active and then restarted JMRI. Skinny windows for the settings window and other windows such as all of the edit windows. I closed JMRI and unplugged the secondary monitor. Restart JMRI and everything appeared to work OK. I re-plugged in the second monitor and everything still appears to work as it has for years. I copied a tables file with a lot of data (turnouts, sensors, blocks, signals, LogixNG, etc) into the new profile. Restart JMRI and loaded the new tables file. Everything appears to display fine and all of the edit dialogs are full size as they should be.
?
So, it's a little inconvenient to create a new profile but that's a rare event, of course. Most of the functionality is working OK so far so this is very usable. I'll keep plucking away and report back if any showstoppers crop up in the future.
?
Thanks for the help, Dave.
?
Vince
 

Vince,

That is some really weird behavior.

If you are interested, rename or move the user-interface.xml file and see what happens.

Dave Sand


----- Original message -----
From: "Vince Guarna via groups.io" <vince=[email protected]>
Subject: Re: [jmriusers] Edit dialog boxes do not open with full width
Date: Tuesday, May 20, 2025 2:20 PM

Following up: I created a new config profile with both monitors plugged in. I'm leaving everything in the default location (~/Library/Preferences/JMRI/<profile>.jmri)? now even though I had no problem with that in the past. I set the new profile as active and then restarted JMRI. Skinny windows for the settings window and other windows such as all of the edit windows. I closed JMRI and unplugged the secondary monitor. Restart JMRI and everything appeared to work OK. I re-plugged in the second monitor and everything still appears to work as it has for years. I copied a tables file with a lot of data (turnouts, sensors, blocks, signals, LogixNG, etc) into the new profile. Restart JMRI and loaded the new tables file. Everything appears to display fine and all of the edit dialogs are full size as they should be.
?
So, it's a little inconvenient to create a new profile but that's a rare event, of course. Most of the functionality is working OK so far so this is very usable. I'll keep plucking away and report back if any showstoppers crop up in the future.
?
Thanks for the help, Dave.
?
Vince
 

Yes, even though it appears I now have a workaround for the problem, I'm definitely interested in poking around some more to get to the bottom of this. I tried the experiment you mentioned with my "working" My_JMRI_Railroad profile (renaming the user-interface.xml file, moving out the .bak files, just in case). Both monitors plugged in. I tried editing a turnout and I get a skinny window. Save it and re-edit, skinny window again.
?
I won't have a lot of time today, but I'm now at least somewhat motivated to see if I can help. I'll try some more experiments, including comparisons with the files in my older X86/Java 11 system, to see if I can gain any insights. Might be an opportunity for me to accidentally learning something while sniffing around in the UUID folder.
?
Will report back when I have something potentially interesting.
?
Vince
 

¿ªÔÆÌåÓý

Vince,

?

The user-interface.xml getting some odd values in there is a typical cause. Since removing the user-interface.xml which holds things like last size didn¡¯t really work, my guess would be the screen size is not being reported right somehow. There might be debug that you could turn on that would show it thinking ¡°this tool is X wide, the user preference is Y wide, but the screen says it¡¯s only Z wide¡± and that would confirm what going on.

?

But in your screen settings things like magnify or scale might impact this. Also, some hi-res screens run on low res settings can also confuse things sometimes.

?

Others may have clues on this.

?

-Ken Cameron, Member JMRI Dev Team

?

?
 

Thanks, Ken. It sure does appear to act as you suggested. Here's a potentially interesting data point. Since I'm lucky enough to have two Macs both running 5.10 but on different platforms, I tried a simple A/B test. On my Studio (current, new machine - acting weirdly), I started up JMRI and opted to create a new profile called "foo". After clicking OK, it opens up the preferences window as well as the startup PanelPro dialog. Both are "skinny" (see the original post below). Without doing anything else, I went into the profile folder and "vi"ed the user-interface.xml file. Then I went to the iMac (older but working system) and did the same thing. Here are the two xml files:
?
First, the .xml file from the new, misbehaving system:
?

<?xml version="1.0" encoding="UTF-8"?>

<auxiliary-configuration xmlns="http://www.netbeans.org/ns/auxiliary-configuration/1">

? ? <classPreferences xmlns="http://jmri.org/xml/schema/auxiliary-configuration/class-preferences-4-3-5.xsd">

? ? ? ? ? ?(deleted - they're identical between the two files

? ? </classPreferences>

? ? <windowDetails xmlns="http://jmri.org/xml/schema/auxiliary-configuration/window-details-4-3-5.xsd">

? ? ? ? <window xmlns="" class="apps.gui3.tabbedpreferences.TabbedPreferencesFrame:Preferences" height="1440.0" locX="-654.0" locY="0.0" width="80.0"/>

? ? ? ? <window xmlns="" class="PanelPro" height="237.0" locX="48.0" locY="583.0" width="80.0"/>

? ? ? ? <window xmlns="" class="jmri.jmrit.roster.Roster"/>

? ? </windowDetails>

</auxiliary-configuration>

?

Now, the .xml file from the old, working system:

<?xml version="1.0" encoding="UTF-8"?>

<auxiliary-configuration xmlns="http://www.netbeans.org/ns/auxiliary-configuration/1">

? ? <classPreferences xmlns="http://jmri.org/xml/schema/auxiliary-configuration/class-preferences-4-3-5.xsd">

? ? ? ? ? ? ? (again deleted - same as new file)

? ? </classPreferences>

? ? <windowDetails xmlns="http://jmri.org/xml/schema/auxiliary-configuration/window-details-4-3-5.xsd">

? ? ? ? <window xmlns="" class="jmri.jmrit.roster.Roster"/>

? ? ? ? <window xmlns="" class="apps.gui3.tabbedpreferences.TabbedPreferencesFrame:Preferences" height="1440.0" locX="147.0" locY="0.0" width="1018.0"/>

? ? ? ? <window xmlns="" class="PanelPro" height="237.0" locX="1025.0" locY="601.0" width="510.0"/>

? ? </windowDetails>

</auxiliary-configuration>

?

Notice that in the first, incorrect file, the width for both the Preferences window and the opening PanelPro window tags is "80.0". For the working system, the Preferences window width is set to "1018.0" and the width for the PanelPro window is "510.0". On both systems, the width in the .xml file appear to correctly match the windows that appear on the screen. In fact, it looks like all "skinny" windows are 80 [pixels] wide. (When they open, I line them up with each other to check it out.) Not sure where that 80 comes from. One random thought I had was that 80 is frequently the default width (in characters, not pixels) of a terminal window (24x80). Maybe just a meaningless coincidence, but it did come to mind.

Maybe another thing worth noting is the locX property in the "bad" file. The Preferences? window tag has a locX property of -654.0 and the PanelPro has a locX of 48.0. On the screen, the PanelPro pane is on my main monitor. The Preference pane is painted on the secondary monitor. I have the Mac configured so that the main monitor is on the right side of my desk and the secondary is on the left. This then looks as though the coordinate system is based on the main monitor and the negative locX for the Preferences panel reflects the fact that it is to the left of the main monitor (whose left screen edge would represent x = 0).

A couple of other things that come to mind. The new system (with the problem) is a Mac Studio with two monitors. The old, working system is an iMac with a 5K display. Prior to getting the Studio, I used this same Thunderbolt monitor (located on the left as it is now with the new system). I don't remember ever having "skinny window" problems with that system. Perhaps there is a difference between how Apple reports screen geometries between a headless system. with two monitors and an all-in-one computer with one monitor.

The iMac now has no second monitor. So, any tests I run at this point will not be an exact apples-to-apples comparison (no pun intended...although I like it? :-0 ) And, as we appear to be seeing now, even the new system (Studio) works with only one monitor attached.

Please feel free if there are some tests you would like to see run. I am eager to help if I can.

Vince
 

¿ªÔÆÌåÓý

Vince,

?

Here is a clue.

jmri.util.JmriJFrame

?

If you set that to TRACE level, it will show more of how it is figuring out size stuff. Might not get you an answer but worth a shot.

?

Debug->Display/Edit Log Categories

At the bottom scroll box, go down the list to:

jmri.util.JmriJFrame

then pick TRACE in the ¡®New level for above category¡¯ pull down.

?

I¡¯m suspecting that something is saying the screen is way smaller and that confuses everything.

?

-Ken Cameron, Member JMRI Dev Team

?

?
 

Ken,
?
Attached are a couple of traces. They are really traces of the same activity but I noticed something interesting. Process was:
?
  1. Start JMRI
  2. Select profile "foo"
  3. Open the Display/Edit Log Categories pane
  4. Set the logging level to TRACE for jmri.util.JmriJFrame
  5. Close the Display/Edit Log pane
  6. Open the Console pane. (It's skinny the very first time opened after the profile is created but JMRI remembers the geometry after that)
  7. Open Tools -> Tables -> Turnouts (this pane is never skinny...looks fine and retains any new size or position I give it)
  8. Click "Add..." in the Turnout Table.
  9. Skinny edit pane appears. Changing the size by hand is never remembered by JMRI
  10. Copy and paste the log into a text file
You'll notice in the log that I put a blank line between steps 5 and 6 and also between steps 7 and 8 just for clarity.
?
I looked over the log and noticed references to screens 3 and 5. That reminded me that I'm running three desktops on the system. So, effectively, 6 monitors, so 3 and 5 would make sense. Seemed promising....maybe the OS is fetching screen sizes for screens that are not displayed and therefore zero? The trace named "JMRI_Trace_3_Desktops.txt" was captured running in this configuration.
?
To test the question of whether 3 desktops were the problem, I deleted desktops 2 and 3 and reran JMRI. Oddly, the log still showed references to screens 3 and 5. So, I rebooted the system and tried again. This time the log showed references to screen 1 and 2. You can see that in the other trace ("JMRI_Trace_1_Desktop.txt").
?
That's it for now. BTW, I also run desktops on the older system and did not have any problems.
?
Vince

JMRI_Trace_3_Desktops.txt
JMRI_Trace_3_Desktops.txt
JMRI_Trace_1_Desktop.txt
JMRI_Trace_1_Desktop.txt

1 - 16 of 16