On 24-12-20 8:53 PM, Simon Ser wrote:
On Friday, December 20th, 2024 at 10:46, Campbell Barton
wrote:
Instead, we've standardized a protocol to set semantic cursor shapes:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main/staging/cursor-shape?ref_type=heads
Does that help?
On Friday, December 20th, 2024 at 10:46, Campbell Barton
wrote:
> > Instead, we've standardized a protocol to set semantic cursor shapes:
> > https://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main/staging/cursor-shape?ref_type=heads
> >
> > Does that help?
>
> It's not a solution
On 24-12-20 7:48 PM, Simon Ser wrote:
Hi!
This has been discussed before, with an XCursor configuration protocol
proposal:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/21
However that approach turned out to be quite complex, and a bit
backwards (back-and-forth an
On Fri, Dec 20, 2024 at 01:07:27PM +1100, Campbell Barton wrote:
> Hi, I've been maintaining Blender's Wayland integration and have run into
> issues with cursor size being too big/small.
>
> At first I thought it could be overlooked (treated as more of a glitch),
> however in the worst case this
Hi!
This has been discussed before, with an XCursor configuration protocol
proposal:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/21
However that approach turned out to be quite complex, and a bit
backwards (back-and-forth and duplicated work in compositors and client
Hi, I've been maintaining Blender's Wayland integration and have run
into issues with cursor size being too big/small.
At first I thought it could be overlooked (treated as more of a glitch),
however in the worst case this is an accessibility issue, one user for
example found the cursor was so s
