Station Configuration Crashing when adding new hardware
Re: Station Configuration Crashing when adding new hardware
That takes me back, we used to have a Matrox RT suite in one of our Offline edit suites along with a Canopus system as well.
Fat Finger Typing can often cause things to break!! 
Re: Station Configuration Crashing when adding new hardware
I've had the exact same issue.
I'm a new Log4OM user, just installed v2.11.0.0. When trying to set my Station Configuration for the first time and add my radio information, the application seemed to lock up. Like 2E1ART, I found that if I pressed the ESC key, it brought me back to the Configuration window. So, the entry field was opening up, but I couldn't see it. I searched the forum for "Station Configuration", found this post and tried moving my Log4OM Window to my primary monitor and it worked! Not only that, but it then occurred to me where the problem might lie.
For reference, I'm using a laptop with one (older) external 1080p monitor connected via an HDMI to DVI cable. My external monitor is actually set as my "main display." However, my laptop screen is "3k" (2880x1620). I've seen strange GUI issues like this before, when a Windows 10 system is running multiple displays of differing resolutions. The culprit here is the Display Scaling. Settings --> System --> Display --> Scale and layout. By default, Windows 10 sets the scale of higher resolution displays at greater than 100% (Usually 150% or 200%, depending on resolution). I imagine this is so your text and icons don't look so tiny. However, if you have one 1080p display set at 100% scaling, and one or two external 4k displays set at 200% scaling, you'll get some really funky problems. This usually happens with applications that aren't properly coded to respect display scaling, but even ones that do (like Log4OM) can suffer. Display scaling in Windows 10 is kind of a mess.
I found that if I set the display scaling to 100% on both of my displays, the new radio entry box pops up as expected. I've noticed that this entry box is anchored, and I'm not sure how you define it's placement in the program code, but maybe this insight could lead to a solution. Regardless, I hope that I've at least helped someone with a more permanent work-around.
73,
Jay W2OG
I'm a new Log4OM user, just installed v2.11.0.0. When trying to set my Station Configuration for the first time and add my radio information, the application seemed to lock up. Like 2E1ART, I found that if I pressed the ESC key, it brought me back to the Configuration window. So, the entry field was opening up, but I couldn't see it. I searched the forum for "Station Configuration", found this post and tried moving my Log4OM Window to my primary monitor and it worked! Not only that, but it then occurred to me where the problem might lie.
For reference, I'm using a laptop with one (older) external 1080p monitor connected via an HDMI to DVI cable. My external monitor is actually set as my "main display." However, my laptop screen is "3k" (2880x1620). I've seen strange GUI issues like this before, when a Windows 10 system is running multiple displays of differing resolutions. The culprit here is the Display Scaling. Settings --> System --> Display --> Scale and layout. By default, Windows 10 sets the scale of higher resolution displays at greater than 100% (Usually 150% or 200%, depending on resolution). I imagine this is so your text and icons don't look so tiny. However, if you have one 1080p display set at 100% scaling, and one or two external 4k displays set at 200% scaling, you'll get some really funky problems. This usually happens with applications that aren't properly coded to respect display scaling, but even ones that do (like Log4OM) can suffer. Display scaling in Windows 10 is kind of a mess.
I found that if I set the display scaling to 100% on both of my displays, the new radio entry box pops up as expected. I've noticed that this entry box is anchored, and I'm not sure how you define it's placement in the program code, but maybe this insight could lead to a solution. Regardless, I hope that I've at least helped someone with a more permanent work-around.
73,
Jay W2OG
