I am aware on Wayland the application is not aware of (nor can manage) it’s window(s) geometries, and with gtk4 accessing this info already got removed and the only way (on X11) is to fall back to native X11 calls.
I am reading in the “Wayland book” to get some more background why and what may be a solution.
“However, a deliberate design trait of Wayland makes application windows ignorant of their exact placement on screen or relative to other windows. This decision affords Wayland compositors a greater deal of flexibility — windows could be shown in several places at once, arranged in the 3D space of a VR scene, or presented in any other novel way. Wayland is designed to be generic and widely applicable to many devices and form factors.” Then mentions some XDG stuff to possibly access this?? I have not clue about at this time.
Well, if you ever 3d (even I do not see that been useful for most application “windows”) – just give me a Z coordinate as well
So my design problem is a application having more than a single “main window” but also numerous additional window for various tasks, and depending on operation tasks they may be more or less frequently required.
The user normally arranges everything as it fits best his needs. (I am talking about 10 or more plus some varying number of data/image views) – best having them side by side on two or three screens. Generally a big “dash board” for operations.
Now you may imaging once comfortable arranged, it is more than convenient but necessary to store and restore the window layout at next start startup. Now you may say I could use a single huge application window and manage things inside – but why shall I copy that work of a window manager?