[PATCH] Fixes v5: Cursor barriers

[Daniel Stone]

On Tue, Dec 07, 2010 at 11:26:18AM +1000, Peter Hutterer wrote:
> On Mon, Nov 15, 2010 at 05:11:54PM -0500, Adam Jackson wrote:
> > +CreateCursorBarrier
> > +
> > +		barrier:		    BARRIER
> > +		window:			    WINDOW
> > +		x1, y2, x2, y2:		    CARD16
> > +		directions:		    CARD32
> > +
> > +	Creates a cursor barrier along the line specified by the given
> > +	coordinates on the screen specified by the given Window.  The
> > +	barrier has no spatial extent; it is simply a line along the left
> > +	or top edge of the specified pixels.
> > +
> > +	The coordinates must be axis aligned, either x1 == x2, or
> > +	y1 == y2.  If not, BadValue is generated.
> > +
> > +	Motion is allowed through the barrier in the directions specified.
> > +	Nonsensical values (forbidding Y axis travel through a vertical
> > +	barrier, for example) and excess set bits are ignored.
> > +
> > +	Servers supporting the X Input Extension version 2.0 or higher
> > +	respect these barriers for any cursor on relative motion events.
> > +	Absolute positioning devices do not obey these barriers as there's
> > +	no benefit to target acquisition to do so.
> 
> Is it worth making it a per-device barrier with the usual XIAllDevices,
> XIAllMasterDevices. Though it could be interesting handling a blocked master
> device on a non-blocked SD...

Since the intent is to constrain a pointer, might as well only allow
constraints for MDs, given that's where the sprite lives.

Cheers,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101207/1043001b/attachment.pgp>