RFC: sorting out grabs

[Daniel Stone]

On Thu, May 10, 2007 at 08:45:55PM +0930, Peter Hutterer wrote:
> == Multiple grabs - yes or no ===
> MPX removes the notion of the core pointer/keyboard. A device can send 
> core events** or not, but all pointers/keyboards are equal.
> Should we continue to allow two grabs on the devices or only one?
> 
> To be more precise, if a client core-grabs a device, should the device 
> be grab-able by an other client for XI events? And the other way round 
> of course.

I'd say no: extend device grabs to include the entire spectrum.  If you
device-grab a given keyboard, then it shouldn't emit any core events to
anyone but that client, if it's selected for it.

> I would like to remove the double-grab feature and go back to one. Comments?

Sounds good to me.

> At the moment, the grab behaviour is the following:
> When a client C has a grab on pointer X or keyboard Y:
>    X/Y _only_ send to C.
>    any other device Z can send to all clients but C.
>    Z will not send events to C, except
>    if Z is a pointer and the event.window == grabWindow, Z sends to C.
> (The last made popup menu less painful if you don't have a MPX aware WM)
> 
> This works ok, but as I said, it changes the notion of a grab. Right 
> now, the notion is along the lines of  "Don't deliver events to anybody 
> but me". With those changes the notion is more like "I want to get 
> exclusively get events from device X".
> 
> Comments?

Hmmm.  I'm honestly not sure what the semantics should be here.

Cheers,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg/attachments/20070510/3e65fe93/attachment.pgp>