action binder protocol https://git.vlhl.dev/navi/wayland/wayland-protocols.git/atom?h=master 2023-06-20T01:11:54+00:00 2023-06-20T01:11:54+00:00 Anna (navi) Figueiredo Gomes navi@vlhl.dev 2023-06-19T16:48:29+00:00 urn:sha1:64716493d19bc0f7c875b3f907b37e3c530558f8 Signed-off-by: Anna (navi) Figueiredo Gomes <navi@vlhl.dev> 2023-06-19T15:59:41+00:00 Quentin Glidic sardemff7+git@sardemff7.net 2017-08-16T19:19:06+00:00 urn:sha1:24798c8fc0cacd57754fac9fceff265be15fbda0 Signed-off-by: Quentin Glidic <sardemff7+git@sardemff7.net> 2023-05-09T09:59:35+00:00 Simon Ser contact@emersion.fr 2023-05-09T09:59:35+00:00 urn:sha1:18aa7b27f7ef3ee024f3fbc3818b75176a10a692 This interface has no "enter" event. This was likely copy-pasted from wl_pointer.set_cursor. The event which indicates focus is proximity_in. Signed-off-by: Simon Ser <contact@emersion.fr> 2023-04-18T12:06:04+00:00 Vlad Zahorodnii vlad.zahorodnii@kde.org 2023-04-18T11:59:56+00:00 urn:sha1:fefd185994bdf6673e86a89ae5c63987841dbb6c There are no interfaces such as zlinux_dmabuf_params and zlinux_buffer_params. Signed-off-by: Vlad Zahorodnii <vlad.zahorodnii@kde.org> 2023-03-30T20:47:28+00:00 Mikhail Gusarov dottedmag@dottedmag.net 2022-10-20T22:17:38+00:00 urn:sha1:275fce4af9b6008a372933dfa5109553e6348dd1 Make it explicit in the protocol that [un]set_maximized and the following configure event can't be reliably matched, and the clients shouldn't try to do it. Closes #106 Signed-off-by: Mikhail Gusarov <dottedmag@dottedmag.net> 2023-03-30T15:44:07+00:00 Xaver Hugl xaver.hugl@gmail.com 2022-08-16T12:48:44+00:00 urn:sha1:5c274ffc9068da85e08d6144e1304c3b9e0c932f Signed-off-by: Xaver Hugl <xaver.hugl@gmail.com> 2023-02-27T11:26:25+00:00 Jonas Ådahl jadahl@gmail.com 2023-02-21T12:24:51+00:00 urn:sha1:94482ceaf9be9a128065358aa56f631e3a118f75 The "logical size" as stated by the first paragraph corresponds to the monitor size in the global compositor space. To most clients, this is unnecessary information, and should be ignored, but some used the listed examples to derive information that contradicts the very definition of what this event communicates. One example tried to add surface size assumptions, which was not correct. Remove this part completely, clients should not try to configure their surface sizes from the logical size of a monitor. The other is the list of size examples; it tried to communicate that a compositor sometimes may not scale the viewport of the monitor in its global compositor coordinate space, in which case, the logical size itself matches the actual resolution. Tweak this wording to make that clear that it does not related to any surface size. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> 2023-02-21T12:31:18+00:00 Simon Ser contact@emersion.fr 2023-02-03T08:26:20+00:00 urn:sha1:cf838fd316f74b0a79ca6cbe1a5cf2548c8265c2 In the past, xdg-output had only the logical_position and logical_size events, then the name and description events were added. Later on, they were moved inside wl_output since they aren't desktop-specific. However the goals section of the protocol overview hasn't been updated accordingly. Make it clear that this protocol's name and description events should not be preferred over wl_output. Signed-off-by: Simon Ser <contact@emersion.fr> 2023-02-12T10:16:21+00:00 Simon Ser contact@emersion.fr 2023-02-02T13:56:16+00:00 urn:sha1:380bdd6ba7ed836412ef5e5d6385fd45151e8489 These have been merged into wl_output. Clients should prefer using wl_output events instead of relying on xdg-output. Signed-off-by: Simon Ser <contact@emersion.fr> 2022-11-14T11:08:21+00:00 Manuel Stoeckl code@mstoeckl.com 2022-11-02T23:01:44+00:00 urn:sha1:4f18a5baeece5e37c31164af42bcc20b8460727f Signed-off-by: Manuel Stoeckl <code@mstoeckl.com>