[Qmidiarp-user] Issue with window state and missing Arps

[Lorenzo S. <lor...@gm...>]

Hi,

I'm not sure if this mailing list is still active as I see the last 
message in the archive is from 2020...

Anyway I have a session with two arpeggiators and two sequencers which 
I'd like to possibly use live.

  When I created the session and worked on it all of the modules were 
correctly displayed in the tabs just below the settings (mid window if 
maximised)

When I reloaded all the display was mangled and 'maximised' to a size 
larger than the screen.

Essentially after trying to reset the visialisation I managed to have 
the arps disappear and couldn't figure out how to show them again.

As a work-around I was able to have a 'normal' view by manually editing 
the XML file and remove everything in the <windowState> tag, then 
restarting qmidiarp and loading the .qmax file.

The issue is that when closing qmidiarp (even without saving) and 
re-opening the file that <windowState> tag is modified and this makes 
the session un-usalbe again.

One thing I noticed is that the application also stars with a rather 
small window and if I maximised or window size changed this is nor 
retained on next run. I did notice a setting GUIState in the .qmidiarprc 
file but have no idea how it works and if it should 'remember' the 
window size (besideds the loaded session).

I/ _am_ /using wayland on my system (KDE Plasma 6.3.5 with 6.9.1) and I 
see a bunch of errors / warnings if I run the application from the 
command line. In particular this error seems to be relevant as it comes 
up when reloading the file and _if_ the windowState tag containse something:

qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

I also did try running with QT_QPA_PLATFORM=xcb but I'm still getting 
this issue (although no wayland errors displayed)

The only (ugly( hack which works is to make the .qmax file readonly so 
that when qmidiarp is closed it cannot change the <windowState> tag, 
maybe I could even hack a script which 'cleans' the tag before loading, 
but that's not optimal if I needed to actually modify the session and 
save it :)

Any hint or idea is welcome.

Thanks

Lorenzo