On Thu, Jun 04, 2015 at 05:05:55PM +0800, Jonas Ådahl wrote:
> On Fri, May 29, 2015 at 09:23:29AM +1000, Peter Hutterer wrote:
> > On Wed, May 13, 2015 at 06:26:35PM +0800, Jonas Ådahl wrote:
> > > This patch introduces a new protocol for locking and confining a
> > > pointer. It consists of a new
On Fri, May 29, 2015 at 09:23:29AM +1000, Peter Hutterer wrote:
> On Wed, May 13, 2015 at 06:26:35PM +0800, Jonas Ådahl wrote:
> > This patch introduces a new protocol for locking and confining a
> > pointer. It consists of a new global object with two requests; one for
> > locking the surface to a
On Wed, May 13, 2015 at 06:26:35PM +0800, Jonas Ådahl wrote:
> This patch introduces a new protocol for locking and confining a
> pointer. It consists of a new global object with two requests; one for
> locking the surface to a position, one for confining the pointer to a
> given region.
>
> See p
On 05/14/2015 07:53 PM, Jonas Ådahl wrote:
but your notes were very misleading.
What notes?
The statement "Serials are dropped" that was in your header email is the
one that really threw me.
The primary problem I am having is all your description seems to be for
setting up something li
On Thu, May 14, 2015 at 12:26:52PM -0700, Bill Spitzak wrote:
> On 05/13/2015 11:34 PM, Jonas Ådahl wrote:
>
> Okay, looking at the clickdot and resizor examples, it appears you are
> actually responding to events with pointer_lock. This is pretty much what I
> think makes sense but your notes wer
On 05/13/2015 11:34 PM, Jonas Ådahl wrote:
Okay, looking at the clickdot and resizor examples, it appears you are
actually responding to events with pointer_lock. This is pretty much
what I think makes sense but your notes were very misleading.
The primary problem is that you removed the seri
On Wed, May 13, 2015 at 12:50:33PM -0700, Bill Spitzak wrote:
> Again this seems excessively complicated, requires lots of communication
> long before the lock happens, makes the methods used to trigger the lock
> very limited and dependent on compositor features, and it does not look like
> it is
Again this seems excessively complicated, requires lots of communication
long before the lock happens, makes the methods used to trigger the lock
very limited and dependent on compositor features, and it does not look
like it is possible to avoid an unwanted blink in the cursor.
- Client must
This patch introduces a new protocol for locking and confining a
pointer. It consists of a new global object with two requests; one for
locking the surface to a position, one for confining the pointer to a
given region.
See pointer-lock.xml for details of the protocol.
In this patch, only the loc
