mirror of https://github.com/swaywm/sway.git
6ea45395c7
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. |
||
|---|---|---|
| .. | ||
| cursor.c | ||
| input-manager.c | ||
| keyboard.c | ||
| libinput.c | ||
| seat.c | ||
| seatop_default.c | ||
| seatop_down.c | ||
| seatop_move_floating.c | ||
| seatop_move_tiling.c | ||
| seatop_resize_floating.c | ||
| seatop_resize_tiling.c | ||
| switch.c | ||
| tablet.c | ||
| text_input.c | ||