fork of wlroots with action binder support https://git.vlhl.dev/navi/wayland/wlroots.git/atom?h=master 2024-02-23T17:46:25+00:00 2024-02-23T17:46:25+00:00 John Lindgren john@jlindgren.net 2024-02-12T23:37:55+00:00 urn:sha1:2521fba37c396909eec6da88070ec9111aa2c507 For XWayland surfaces that start maximized, it's best to send an initial Configure event to set the size of the surface before mapping it. This reduces visual glitches since the application sees the correct maximized size when performing its initial layout and drawing. wlroots surfaces emit their first "map" event after the XWayland window has already been mapped and the first frame has been drawn & committed. This is too late to send the initial Configure event. So, add a new "map_request" event which is emitted immediately before telling XWayland to map the window. Compositors can connect to this event to send the initial Configure event to an XWayland app based on its requested maximized (or fullscreen) state. Compositors should not place anything visually on the screen at this point but rather wait until the "map" event as before. 2023-10-26T19:05:08+00:00 John Lindgren john@jlindgren.net 2023-10-24T14:33:50+00:00 urn:sha1:af165acb427dd166f2768cf806d28f106bc61fd7 This function allows compositors to set the _NET_WORKAREA property on the root window. XWayland clients use _NET_WORKAREA to determine how much of the screen is not covered by panels/docks. The property is used for example by Qt to determine areas of the screen that popup menus should not overlap (see QScreen::availableVirtualGeometry). 2023-10-15T01:27:34+00:00 John Lindgren john@jlindgren.net 2023-10-11T07:37:46+00:00 urn:sha1:6114dd6a838c1c4ebeb5c8f2a66f7c1e628d11d5 Translating the right/bottom coordinates from offsets to absolute coordinates in wlroots (rather than in the compositor) was supposed to be more reliable, since wlroots had access to the X11 screen size. It ended up being less reliable, because the screen size values (xwm->screen->width_in_pixels/height_in_pixels) are not updated when the output layout changes. So let's remove the translation from wlroots, and let the compositor figure it out. From what I can understand of the current XWayland code, the X11 screen size should generally match the overall wlr_output_layout bounding box, which the compositor has access to. 2023-10-10T15:05:04+00:00 Simon Ser contact@emersion.fr 2023-10-09T08:58:00+00:00 urn:sha1:e519635cc265abd9e1240c101dc293a06a78e359 Allows compositors to set up the server (and shell) on their own. 2023-10-10T15:05:04+00:00 Simon Ser contact@emersion.fr 2023-10-10T14:56:11+00:00 urn:sha1:bdcf997a8985831fcd88c018e92acab6a9a5ed5c Allows one to check whether the server is currently ready. 2023-10-06T08:04:11+00:00 JiDe Zhang zccrs@live.com 2023-09-08T13:36:56+00:00 urn:sha1:ca19014af011f5a6433fb6763fa1350c03a77f65 2023-10-02T19:10:16+00:00 Kirill Primak vyivel@eclair.cafe 2023-10-02T19:06:44+00:00 urn:sha1:a09d6494397bdd28a3254d2e646212afb5a3049c 2023-08-03T03:19:35+00:00 Simon Ser contact@emersion.fr 2023-07-28T12:26:35+00:00 urn:sha1:77dc1c28aa551616521b60f1a8727a25a45f82e1 The PID of an X11 window cannot change. This is a remnant from the days when we queried the PID with a window property, instead of using XRes. 2023-07-26T20:31:03+00:00 Kirill Primak vyivel@eclair.cafe 2023-07-26T20:18:45+00:00 urn:sha1:529f1b82ee73939071eb9fd59cbd9318d47d2525 The wlr_xwayland_surface_v1 will be destroyed automatically from xwl_surface_role_destroy(). 2023-07-09T09:48:51+00:00 Simon Ser contact@emersion.fr 2023-07-09T09:48:51+00:00 urn:sha1:5bb005779484967d0b9824aa88563b661a70be51