xserver-multidpi/hw/xwayland
Carlos Garnacho 2172714c67 xwayland: Only disable/enable devices on capabilities change
Anytime a capability is first reported, the device is created, but after
that, it is only disabled/enabled.

This is a closer behavior to what Xorg does on VT switch, at the expense
of maybe leaving a dangling "physical" device if a capability goes for good.
Otherwise, any DeviceIntPtr (re)created after server initialization will be
left floating, and bad things happen when the wayland enter event handler
tries to update cursor position based on a floating device.

Signed-off-by: Carlos Garnacho <carlosg@gnome.org>
Reviewed-by: Daniel Stone <daniel@fooishbar.org>
Signed-off-by: Keith Packard <keithp@keithp.com>
2014-07-24 16:52:41 -07:00
..
.gitignore Xwayland DDX 2014-04-03 15:19:22 -07:00
drm.xml xwayland: Add glamor and DRI3 support 2014-06-24 15:09:55 -07:00
Makefile.am xwayland: Add glamor and DRI3 support 2014-06-24 15:09:55 -07:00
xwayland-cursor.c Xwayland DDX 2014-04-03 15:19:22 -07:00
xwayland-cvt.c Xwayland DDX 2014-04-03 15:19:22 -07:00
xwayland-glamor.c xwayland: Add glamor and DRI3 support 2014-06-24 15:09:55 -07:00
xwayland-input.c xwayland: Only disable/enable devices on capabilities change 2014-07-24 16:52:41 -07:00
xwayland-output.c Xwayland DDX 2014-04-03 15:19:22 -07:00
xwayland-shm.c Xwayland DDX 2014-04-03 15:19:22 -07:00
xwayland.c xwayland: Add glamor and DRI3 support 2014-06-24 15:09:55 -07:00
xwayland.h xwayland: Add glamor and DRI3 support 2014-06-24 15:09:55 -07:00