Originally posted by debianxfce
View Post
That is why Wayland was started. Wayland has started off with a very bare bone protocol intentionally hopefully to lay down a clean framework.
Some of the problems with X11 come from conflicting protocol defines. The worst rule is the fact the server and wm by X11 protocol is free to change, create, delete anything at any time without telling the application about it. This was important for a network protocol when connection could be lost. So WM moves you window from 0, 0 to 1000,0 and tells you it still at 0,0 and your place a pop up in the wrong place that is legal under X11 protocol.
Wayland protocol might be bar bones but its not a lieing pain that X11 protocol allows. X11 protocol need to be rewritten from the ground up without conflicts and without worst allowances. If the server tells your application something it better remain true.
Try doing absolute position and be true and have the window moving. You will soon work out you want absolute position that is always true to your application. Your application should be moving it windows itself.
Wayland stuff missing starts making sense once you start working out how would you avoid information race conditions. Some things should be processed application side that were processed server/wm side.
Leave a comment: