On Tuesday, October 16, 2018 2:10 PM, Johan Helsing wrote:
> Hi Simon,
>
> Thanks for working on this! :)
Thanks for your feedback! I've sent a first version of this patch. I've
added per-device configuration and addressed your comments. Let me know what
you think.
> Is the intention to implemen
t: Friday, October 12, 2018 7:40:21 PM
To: wayland-devel@lists.freedesktop.org
Cc: Simon Ser
Subject: [PATCH RFC wayland-protocols] unstable: add xcursor-configuration
Clients are responsible for loading and setting cursors. For this
purpose they often use XCursor images via the libwayland-cursor
library
Hi Michael,
Thanks for you comments! Replies below.
On Sunday, October 14, 2018 4:05 AM, Michael Arnold wrote:
> Step 3: When the application exists, if the application has made use of the
> zwp_xcursor_configuration_v1 extension then the application will initiate the
> following conversation wi
Hi,
Sean, this looks great. In the hope that basic questions help, I've
recorded my comments below - apologies if these questions reflection of my
lack of understanding.
My understanding:
Step 1: When an application loads, the application will check which
protocol extensions are common between
Clients are responsible for loading and setting cursors. For this
purpose they often use XCursor images via the libwayland-cursor
library. However clients have no way to know the user's preferred
theme and size. This results in inconsistent cursors across
clients (e.g. cursor growing bigger when en
