mutter:wip/xinput2r

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

052e8cc... by Carlos Garnacho on 2011-08-01

frame: disallow frame operations if the popup is open

If some device has a popped up menu, meta_frame_get_flags()
returns 0 to indicate other devices cannot trigger any
actions on the frame.

827999a... by Carlos Garnacho on 2011-08-01

ui: Add a MetaDevice arg to meta_window_menu_popup()

This will be the device popping up the menu, gtk_menu_popup()
uses the current GTK+ event device, and that might not even be
filled up with mutter event bypassing.

54a58bd... by Carlos Garnacho on 2011-08-01

window: Make MetaWindow keep a pointer to the popup menu

Multiple windows may now have different popup menus, responding
only to the device pair that popped it up.

dc29985... by Carlos Garnacho on 2011-07-26

ui: enable multidevice on frame windows

This is so different pointers may have different
cursors on them.

acbd4bf... by Carlos Garnacho on 2011-07-26

frames: Use the triggering device when updating controls

b742d1b... by Carlos Garnacho on 2011-07-26

frames: Get coordinates from event

Don't spare a synchronous X call, instead translate
properly the XEvent coordinates in ui.c and use
the event coordinates in MetaFrames

ae1290e... by Carlos Garnacho on 2011-07-19

display: Make focus info persistent

It must not be freed (at least meanwhile the device pair
exists), so ensure it's kept around, and we don't create
info for a same keyboard twice.

8037cc5... by Carlos Garnacho on 2011-07-19

window: make guess_grab_pointer() more reliable

Now either the current focus keyboard or the client pointer
(i.e. the pointer paired to the last keyboard that had the
window focus) are used to guess the pointer that should be
grabbed.

275ab90... by Carlos Garnacho on 2011-07-19

window: set the corresponding client pointer on focused windows.

The client window determines the device pair that is used for
core protocol calls such as XQueryPointer(), so different
clients using the core protocol can be focused by different
devices simultaneously.

b3a9d1b... by Carlos Garnacho on 2011-07-09

core: enable XInput2 by default

This is nothing but the beginning, things work with a single
pointer/keyboard pair, but will be largely broken with multiple
devices interacting simultaneously, so we first need a policy
to establish a sensible behavior for extra pointer/keyboard
pairs.

the MUTTER_USE_CORE_DEVICES envvar has been added to force use
of Xlib core events for devices in order to check for regressions.