mirror of
https://github.com/brl/mutter.git
synced 2024-11-24 00:50:42 -05:00
0e758a9e65
We've long used a switch statement on the grab operation to determine where events should go. The issue with MetaGrabOp is that it's a mixture of a few different things, including event routing, state management, and the behavior to choose during operations. This leads to poorly defined event routing and hard-to-follow logic, since it's sometimes unclear what should point where, and our utility methods for determining grab operations apart can be poorly named. To fix this, establish the concept of a "event route", which describes where events should be routed to. |
||
---|---|---|
.. | ||
protocol | ||
meta-wayland-data-device.c | ||
meta-wayland-data-device.h | ||
meta-wayland-keyboard.c | ||
meta-wayland-keyboard.h | ||
meta-wayland-outputs.c | ||
meta-wayland-outputs.h | ||
meta-wayland-pointer.c | ||
meta-wayland-pointer.h | ||
meta-wayland-private.h | ||
meta-wayland-seat.c | ||
meta-wayland-seat.h | ||
meta-wayland-surface.c | ||
meta-wayland-surface.h | ||
meta-wayland-touch.c | ||
meta-wayland-touch.h | ||
meta-wayland-types.h | ||
meta-wayland-versions.h | ||
meta-wayland.c | ||
meta-wayland.h | ||
meta-xwayland-private.h | ||
meta-xwayland.c | ||
meta-xwayland.h | ||
window-wayland.c | ||
window-wayland.h |