[PATCH] xwayland: Only disable/enable devices on capabilities change

2014-07-22 Thread Carlos Garnacho
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

[PATCH] xwayland: Only disable/enable devices on capabilities change

2014-07-22 Thread Carlos Garnacho
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

Re: [PATCH] xwayland: Only disable/enable devices on capabilities change

2014-07-22 Thread Daniel Stone
Hi, On 22 July 2014 16:55, Carlos Garnacho wrote: > 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 capa

Re: [PATCH] xwayland: Only disable/enable devices on capabilities change

2014-07-24 Thread Keith Packard
Carlos Garnacho writes: > 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. > Oth