Ryan Dwyer bdac0df4f8 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.		2019-03-04 07:51:22 -07:00
..
cursor.c	Allow concurrent clicks	2019-03-04 07:51:22 -07:00
input-manager.c	seat_cmd_cursor: do not create non-existing seat	2019-02-03 14:01:29 -05:00
keyboard.c	input/keyboard: respect solo repeat_{rate,delay}	2019-02-10 18:45:02 +01:00
seat.c	seat: don't send button release when not pressed	2019-02-28 23:02:06 -05:00
seatop_down.c	Allow concurrent clicks	2019-03-04 07:51:22 -07:00
seatop_move_floating.c	seat: don't send button release when not pressed	2019-02-28 23:02:06 -05:00
seatop_move_tiling.c	seat: don't send button release when not pressed	2019-02-28 23:02:06 -05:00
seatop_resize_floating.c	floating_maximum_size: change default behavior	2019-03-02 09:10:26 +01:00
seatop_resize_tiling.c	seat: don't send button release when not pressed	2019-02-28 23:02:06 -05:00