Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tablet tool cursor image doesn't update on entering v2 surface #5257

Closed
Xyene opened this issue Apr 26, 2020 · 0 comments · Fixed by #5258
Closed

Tablet tool cursor image doesn't update on entering v2 surface #5257

Xyene opened this issue Apr 26, 2020 · 0 comments · Fixed by #5258

Comments

@Xyene
Copy link
Member

Xyene commented Apr 26, 2020

When moving a tablet tool over the resize edge of a v2 surface, the <-> cursor image "sticks" after passing the edge. It remains stuck even during application contexts where it'd be expected to change (e.g. hovering a link in Firefox, or switching to the grab tool in Xournal).

WAYLAND_DEBUG shows that the clients are sending the set_cursor request, and sway logs contain a bunch of:

[sway/input/cursor.c:801] denying request to set cursor from unfocused client 
Xyene added a commit to Xyene/sway that referenced this issue Apr 26, 2020
`handle_tablet_tool_set_cursor` was copied from input/cursor.c's
`handle_request_set_cursor`, but the focused surface check was not
adjusted appropriately.

Fixes swaywm#5257.
Xyene added a commit to Xyene/sway that referenced this issue Apr 26, 2020
`handle_tablet_tool_set_cursor` was copied from input/cursor.c's
`handle_request_set_cursor`, but the focused surface check was not
adjusted appropriately.

Fixes swaywm#5257.
emersion pushed a commit that referenced this issue Apr 26, 2020
`handle_tablet_tool_set_cursor` was copied from input/cursor.c's
`handle_request_set_cursor`, but the focused surface check was not
adjusted appropriately.

Fixes #5257.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant