Screen geometry issues on Arch Linux XFCE

[uilzzw]

Hi @uilzzw

Sorry you're having difficulties.

I'm not seeing this behaviour on any of the Debian or Fedora Linux platforms I normally use for testing - this may be specific to your GUI management environment - though it should be simple to resolve.

Occasionally the main window may extend beyond the current screen dimensions if you add additional widgets to an existing row, but it's generally just a matter of resizing or maximising the window to fit.

Can you provide a little more information, as per the requested Issue Template?

1. Can you confirm that by 'latest release' you mean v1.6.0?
2. Can you confirm your full tkinter version?

   from tkinter import Tcl
   print(Tcl().call("info", "patchlevel"))

3. When you say the window 'keeps expanding', do you mean of its own accord, without any user intervention?
4. Can you provide the FULL TRACEBACK for the 'crash', if possible?
5. Have you tried reverting to the previous version (1.5.23) and, if so, do you still see the issue?
6. Have you actually tried making the change you describe to main.py and, if so, does that definitely resolve the problem?
7. What native screen resolution are you using?

FYI I have a provisional branch for the next release v1.6.1 which includes the ability to save an initial screen geometry (root.geometry(f"{w}x{h}+{x}+{y}") the json config file. That may resolve your issue, but ideally I'd like to see a full error Traceback first.

Anyone else seeing this?

Thanks

Originally posted by @semuadmin in #234

Sorry, I just saw this message today. The following is the situation I encountered.
1.yes

./pygpsclient -V    
pygpsclient 1.6.0

2.tkinter version is 8.6.16

print(Tcl().call("info", "patchlevel"))
8.6.16

3.yes,without any user intervention
4.I cloned the source code and declared an initial window size to tk，Then it will not expand automatically
5. I did not use the previous version. I found that the window would expand from small to large until it crashed. Then I cloned a copy of the source code and declared an initial value for tk.
6.yes，I modified the source code to the following

    root = Tk()
    root.geometry("1800x800") 
    App(root, **kwargs)
    root.mainloop()
    sys.exit()

7. The resolution of my laptop is 1920x1080, and the resolution of the external monitor is 1920x1080.
8. My environment is archlinux+lightdm+xfce4, python venv is 3.11

Thanks

[semuadmin]

I am able to reproduce your issue using pygpsclient==1.6.0, but only on xfce - it appears to work fine with other Arch window managers (e.g. Gnome and Deepin). On xfce the main window expands until the system eventually runs out of pixel memory:

Try installing v1.6.1. This now sets an initial value for the screen geometry at 75% of full screen resolution (it does it in app.py rather than main.py). It also saves the current window geometry to the json config file and restores this on next restart.

I don't 'hard code' the initial screen geometry to a fixed value because different users have different screen configurations. PyGPSClient is designed to work with 'screens' (including VNC remote desktops) as small as 640x480.

It's not a definitive test, but I span up an Arch Linux + lightdm + xfce4 environment in VirtualBox and ran PyGPSClient 1.6.1 - it appears to work fine (I note the font scaling on the banner panel is a bit high but I think that's an XFCE artefact):

[semuadmin]

For yuks I span up another Arch Linux VM running Gnome (rather than xfce) at 1920x1080, and it all appears to work perfectly, with PyGPSClient versions 1.6.0 and 1.6.1:

I'll do further testing on xfce to see if there are any other gotchas, but for now I think updating to 1.6.1 should resolve the immediate issue.

But I'm inclined to recommend using a different window manager if possible - there are plenty of others to choose from!

[uilzzw]

For yuks I span up another Arch Linux VM running Gnome (rather than xfce) at 1920x1080, and it all appears to work perfectly, with PyGPSClient versions 1.6.0 and 1.6.1:

I'll do further testing on xfce to see if there are any other gotchas, but for now I think updating to 1.6.1 should resolve the immediate issue.

But I'm inclined to recommend using a different window manager if possible - there are plenty of others to choose from!

I upgraded to 1.6.1 and found a new problem. The size of the window is calculated according to the resolution of all screens. I have two monitors, both 1920x1080. After initialization and then maximizing, the graphics will be distorted. Can the initial value be calculated based on the resolution of a single screen?For example, the primary display?

xrandr --query
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
HDMI-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 509mm x 286mm
   1920x1080     60.00*+
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
DP-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     60.02*+  48.03  

[semuadmin]

Can the initial value be calculated based on the resolution of a single screen?For example, the primary display

AFAIK Not without invoking platform-specific low level APIs, which introduces unnecessary complexity.

PyGPSClient's main application window is fully resizeable - if you simply resize and reposition the window to suit your preference and save the configuration (via File..Save Configuration), the application will restart in this saved configuration.

After initialization and then maximizing, the graphics will be distorted

The individual user-selectable widgets also dynamically resize, but the 'graphics' only redraw in response to incoming GNSS data (as they are dynamically calibrated against this data). If you start a GNSS connection you'll see the widget 'graphics' will redraw in accordance with the current main window size (assuming your receiver is capable of outputting the specific UBX or NMEA data required by the widget).

[semuadmin]

@uilzzw Did this address your query?