mpv/input
nanahi 65fef73c2b input: don't resolve double clicks on the active mouse section
Normally, key bindings are resolved in the input section stack order.
However, mouse key bindings have a special "active mouse section" feature
(which is a section with MOUSE_MOVE bound and mouse button is down in the
section) which lets the section to be selected instead, with a fallback
to the "default" section. The intention of the feature is for mouse
dragging which should "stick" to the section where the mouse is down.

This causes a problem with scripts which bind mouse double clicks:
since double clicks are triggered on mouse down, it's resolved with the
"active mouse section" feature instead of the section stack order.
If the section which has the double click bound doesn't also have
MOUSE_MOVE bound, the "default" section will be used instead.
If it's already bound there, it will be triggered.

Fix this by not resolving double clicks on the active mouse section, which
is not the intention of the feature.
2024-06-08 23:13:15 +02:00
..
cmd.c input/cmd: add nonrepeatable prefix 2024-05-20 17:47:01 +02:00
cmd.h input: mark a command as canceled if it is explicitly dropped 2024-06-06 23:38:39 +03:00
event.c input: add insert-next support for drag-and-drop 2024-02-26 02:03:21 +00:00
event.h input: add insert-next support for drag-and-drop 2024-02-26 02:03:21 +00:00
input.c input: don't resolve double clicks on the active mouse section 2024-06-08 23:13:15 +02:00
input.h input: add multitouch support functions 2024-05-03 16:14:03 +02:00
ipc-dummy.c
ipc-unix.c
ipc-win.c
ipc.c
keycodes.c various: fix indentation 2024-05-07 11:23:08 +02:00
keycodes.h input: add MP_TOUCH_RELEASE_ALL 2024-05-03 16:14:03 +02:00
meson.build
sdl_gamepad.c