Re: wxPython / Wayland issues

Le 14/01/2021 à 13:51, Matthias Brennwald a écrit :
> Hello
>
> I am writing a GUI application with wxPython, which uses a "main" 
> window with all the controls, and some "secondary" windows where data 
> gets plotted (using matplotlib). I am working mostly on GNOME/Xorg, 
> but recently also was on GNOME/Wayland, where I observed a few issues 
> with my application. I wonder if these issues are related to wxPython, 
> Wayland, or both. Any thoughts or feedback would be welcome!
>
> Specifically, the issues I am observing are:
>
> (1) On Xorg, the windows get arranged nicely next to each other when 
> the application starts. As long as the screen is not too small, they 
> will not overlap each over.
> On Wayland, the windows are just stacked onto each other, covering 
> each other. One has to manually arrange the windows on the screen to 
> avoid the overlaps. As far as I can tell, Wayland does not allow to 
> programmatically position the windows on the screen. However, there 
> must be somethings that I am missing, since the stacked windows are 
> just a mess.
>
> (2) If a long running task is started in my program, the task executes 
> in a separate thread and a "Please Wait..." message is shown as a 
> modal wx.Dialog (as a child of the "main" window). With Xorg, the user 
> can move and resize the "main" and the "secondary" windows on the 
> screen while the thread is running and the modal dialog is shown.
> With Wayland, the windows cannot be moved or resized while the modal 
> dialog is active.
>
> (3) At startup, the application creates empty plot panels in the 
> "secondary" windows. The plot panels get painted correctly on Xorg, 
> but on Wayland some parts are just blank (usually about 20% on the 
> bottom and about 20% on the right). Re-plotting or adding data to the 
> plots does not update the blank parts. Moving the windows on the 
> screen does trigger any update or re-painting. The only way to trigger 
> a proper re-painting of the plot panels is to resize the windows.
>
> Any insights would be greatly appreciated!
>
> Matthias
> -- 
> You received this message because you are subscribed to the Google 
> Groups "wxPython-users" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/wxpython-users/81DXMQ.9MFICIMPXCK13%40gmail.com 
> <https://groups.google.com/d/msgid/wxpython-users/81DXMQ.9MFICIMPXCK13%40gmail.com?utm_medium=email&utm_source=footer>.

Hello Matthias,

I have problems too, but I can't determine the origin ...

(1) On Linux MAGEIA, GNOME/Wayland save programmatically position works 
well with Python 2.7 / wxPython.2.8.12, but does not work on Python 3.8 
/ wxPython 4.1.0 or wxPython 4.1.1. Maybe GTK problem ?

In the same environment, I have another problems (would be reproduced In 
the demo too) with wxGrids on wxPython 4.1.1 and no problem on wxPython 
4.1.0. But with wxPython 4.1.0, many many GTK Warnings.

On Windows, Python 3.8 / wxPython.4.1.0 save programmatically position 
works, no problems with wxGrids, but sometimes all the Python program 
crashes. All work on Python 2.7 / wxPython 2.8.12.

I have not made tests on GNOME/Xorg ...

I imagine the paint is not yet dry, so I hope wxPython 4.1.2 will appear 
soon ... :-)

Hugues JEAN-BAPTISTE


-- 
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/wxpython-users/a724e87c-1e50-9c98-88a7-9d75a1eba453%40agorinfo.fr.