aboutsummaryrefslogtreecommitdiff
path: root/include/sway/input
diff options
context:
space:
mode:
authorTudor Brindus <me@tbrindus.ca>2020-05-20 23:45:43 -0400
committerSimon Ser <contact@emersion.fr>2020-05-28 09:44:00 +0200
commit6ea45395c70939a6d855736cabfe75ad9cf4a0ae (patch)
tree8f5bf05b1e210485aba9c93b4b897dac3310f595 /include/sway/input
parent704d675a36811bdf3de5c95d5e0e7ce2b57b3157 (diff)
input/pointer: send pointer enter event on confine warp
The spec has this to say about sending events on confine creation: Whenever the confinement is activated, it is guaranteed that the surface the pointer is confined to will already have received pointer focus and that the pointer will be within the region passed to the request creating this object. ...and on region update: If warped, a wl_pointer.motion event will be emitted, but no wp_relative_pointer.relative_motion event. Prior to this patch, sway did neither, and updated the hardware cursor position without notifying the underlying surface until the next motion event. This led to inconsistent results, especially in applications that draw their own software cursor.
Diffstat (limited to 'include/sway/input')
0 files changed, 0 insertions, 0 deletions