diff options
author | 2019-03-04 21:04:16 +1000 | |
---|---|---|
committer | 2019-03-04 07:51:22 -0700 | |
commit | bdac0df4f8fd1a816f0cfff8223d54d09823233b (patch) | |
tree | c177fda9b68126ca1011d3ea5f7b96c7a177b437 /meson.build | |
parent | sway.1.scd: document environment vars set by sway (diff) | |
download | sway-bdac0df4f8fd1a816f0cfff8223d54d09823233b.tar.gz sway-bdac0df4f8fd1a816f0cfff8223d54d09823233b.tar.zst sway-bdac0df4f8fd1a816f0cfff8223d54d09823233b.zip |
Allow concurrent clicks
If two cursor buttons are pressed at the same time, the client will now
be notified of the second button press.
The main reason for not sending the concurrent presses was due to an
early return in dispatch_cursor_button if a seatop is in progress. This
patch makes it call seat_pointer_notify_button prior to returning. But
it also has to make sure there's not a mismatch in events such as a
release without a press.
Prior to this patch, the down seatop would send press and release events
in its begin and finish functions. No other seatops did this. A press
event would be sent prior to starting tiling drag, but never an
associated release.
After this patch, no seatops send their own press or release events. We
send them prior to calling the seatop begin functions, then the first
part of dispatch_cursor_button handles all presses during seatops and
when releasing the seatop.
Diffstat (limited to 'meson.build')
0 files changed, 0 insertions, 0 deletions