On Tue, Sep 10, 2019 at 09:49:51PM +0200, Michael Weiser wrote:
> Hello,
>
> I've written a small X client that detects when the pointer hits a
> screen edge in order to trigger actions based on where the edge was hit
> - the classic hot corner use case. The trigger for doing this yet again
> was
On Tue, 10 Sep 2019 21:49:51 +0200 Michael Weiser
said:
> Hello,
>
> I've written a small X client that detects when the pointer hits a
> screen edge in order to trigger actions based on where the edge was hit
> - the classic hot corner use case. The trigger for doing this yet again
> was that
Hello,
I've written a small X client that detects when the pointer hits a
screen edge in order to trigger actions based on where the edge was hit
- the classic hot corner use case. The trigger for doing this yet again
was that all the tools I looked at either polled the pointer position or
Hi allI am new here and hopefully you can help me with my problem. Ive send this mail once, not sure if it got lost or no one could help me so I try again :D. I am trying to useXFixesCreatePointerBarrier and XFixesDestroyPointerBarrierCreating works and I can see how the barrier works. To
Hi allI am new here and hopefully you can help me with my problem. I am trying to useXFixesCreatePointerBarrier and XFixesDestroyPointerBarrierCreating works and I can see how the barrier works. To release the barrier I can catch the events usingXI_BarrierHitXI_BarrierLeavewhich I did and after
Peter Hutterer peter.hutte...@who-t.net writes:
Jasper St. Pierre (14):
cursor: Move pointer barrier code over to XI
barriers: Don't loop over the server to destroy a barrier
barriers: Switch to an explicit hook for barrier constrainment
barriers: Switch to finding
:28:02 +1000)
Jasper St. Pierre (14):
cursor: Move pointer barrier code over to XI
barriers: Don't loop over the server to destroy a barrier
barriers: Switch to an explicit hook for barrier constrainment
n Wed, Dec 12, 2012 at 2:18 AM, Peter Hutterer peter.hutte...@who-t.netwrote:
This is the server-side for the pointer-barrier patches, proposed as XI
2.3.
It adds events for pointer barriers (when the pointer hits vs leaves the
arrier) and the ability to release a pointer across. I hereby
to 1fe6c2ef09bd7422e20ef7f7f8d38f2d773d842b:
Xi: if a MD is removed, send a barrier leave event (if applicable)
(2012-12-17 15:04:11 +1000)
Jasper St. Pierre (14):
cursor: Move pointer barrier code over to XI
barriers: Don't loop over
These are the promised fixes for pointer-barrier events if there is more
than master pointer, plus a fix to avoid accessing recently-freed memory (if
a event is sent after a barrier is destroyed)
Yesterday's series plus these three should conclude the pointer barrier
event/release support
This is the server-side for the pointer-barrier patches, proposed as XI 2.3.
It adds events for pointer barriers (when the pointer hits vs leaves the
arrier) and the ability to release a pointer across. I hereby propose this
for the 1.14 release.
Trees for testing available from:
git
the existing XI infrastructure.
For now, just move a bunch of code over, rename some things, and initialize
the new structures, but still consider it a separate codebase. Pointer barrier
requests are still handled by XFixes, so this is a weird intermediate state.
It's unknown whether we'll add explicit
From: Jasper St. Pierre jstpie...@mecheye.net
This adds support for clients that would like to get a notification
every time a barrier is hit, and allows clients to temporarily release
a barrier so that pointers can go through them, without having to
destroy and recreate barriers.
Based on work
Instead of having the pointer barrier code enqueue events separately from
GetPointerEvents, pass the event list through and let it add to it.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/xibarriers.c | 15 ---
dix/getevents.c | 15 +++
include/input.h
Only deliver to the client that created the barrier, not to other clients.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
dix/events.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/dix/events.c b/dix/events.c
index 3282ef8..49b8bc5 100644
---
barrier events added
- v2.2, March 2012: Multitouch support added
- v2.1, December 2011: new raw event behaviour, smooth scrolling support
added
@@ -57,6 +58,10 @@ Changes in version 2.2
- Multitouch support added
+Changes in version 2.3
+--
+
+- Pointer barrier events
This is the protocol and client-side for the proposed XI 2.3 extension for
pointer barrier events and barrier release requests. This feature adds two
things:
- if a pointer hits a barrier, events are sent to selected clients
- a client may release the pointer, allowing it to pass through
100644
index 000..4fa48fe
--- /dev/null
+++ b/man/XIBarrierReleasePointer.txt
@@ -0,0 +1,76 @@
+XIBARRIERRELEASEPOINTER(libmansuffix)
+=
+
+NAME
+
+
+ XIBarrierReleasePointer, XIBarrierReleasePointers - allow pointer movement
across a pointer barrier
On Tue, Nov 20, 2012 at 02:50:43PM -0500, Jasper St. Pierre wrote:
From: Jasper St. Pierre jstpie...@mecheye.net
This adds support for clients that would like to get a notification
every time a barrier is released, along with a way to temporarily
release a barrier after it has been hit.
the existing XI infrastructure.
For now, just move a bunch of code over, rename some things, and initialize
the new structures, but still consider it a separate codebase. Pointer barrier
requests are still handled by XFixes, so this is a weird intermediate state.
It's unknown whether we'll add explicit
On Sat, Nov 03, 2012 at 06:39:34PM -0400, Jasper St. Pierre wrote:
From: Jasper St. Pierre jstpie...@mecheye.net
This will make it much simpler when we add more error paths to the code
that constructs pointer barrier clients.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
From: Jasper St. Pierre jstpie...@mecheye.net
This will make it much simpler when we add more error paths to the code
that constructs pointer barrier clients.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
xfixes/cursor.c | 54
From: Jasper St. Pierre jstpie...@mecheye.net
This will make it much simpler when we add more error paths to the code
that constructs pointer barrier clients.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
xfixes/cursor.c | 42 --
1 file
: INT16
+ directions: CARD32
+ velocity: CARD32
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated
+ velocity: CARD32
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable. This
+ has identical semantics to CreatePointerBarrier
:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable. This
+ has identical semantics to CreatePointerBarrier, except that the
+ barrier created will not initially block the pointer
:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable. This
+ has identical semantics to CreatePointerBarrier, except that the
+ barrier created will not block the pointer if the threshold
On Thu, 2012-05-03 at 16:35 +1000, Peter Hutterer wrote:
On Thu, May 03, 2012 at 12:40:58PM +1000, Christopher James Halse Rogers
wrote:
On Thu, 2012-05-03 at 11:05 +1000, Peter Hutterer wrote:
On Tue, Apr 03, 2012 at 01:42:38PM +1000, Christopher James Halse Rogers
wrote:
---
On Fri, May 04, 2012 at 09:46:47AM +1000, Christopher James Halse Rogers wrote:
On Thu, 2012-05-03 at 16:35 +1000, Peter Hutterer wrote:
On Thu, May 03, 2012 at 12:40:58PM +1000, Christopher James Halse Rogers
wrote:
On Thu, 2012-05-03 at 11:05 +1000, Peter Hutterer wrote:
On Tue, Apr
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable. This
+ has identical semantics to CreatePointerBarrier, except that the
+ barrier created
: DRAWABLE
+ x1, y2, x2, y2: INT16
+ directions: CARD32
+ velocity: CARD32
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ directions: CARD32
+ velocity: CARD32
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable
+ directions: CARD32
+ velocity: CARD32
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable. This
+ has
On Tue, 2012-04-03 at 13:42 +1000, Christopher James Halse Rogers wrote:
---
I've got a corresponding xserver patch, but it needs updating for the
Great Reindent of '12. Might as well get support for the protocol additions
before fixing it up.
A slightly different variant of this (it's
On Tue, 2012-04-03 at 13:42 +1000, Christopher James Halse Rogers wrote:
---
I've got a corresponding xserver patch, but it needs updating for the
Great Reindent of '12. Might as well get support for the protocol additions
before fixing it up.
A slightly different variant of this (it's
+ devices:LISTofDEVICEID
+
+ Creates a pointer barrier along the line specified by the given
+ coordinates on the screen associated with the given drawable. This
+ has identical semantics to CreatePointerBarrier, except that the
+ barrier created
From: Christopher James Halse Rogers r...@ubuntu.com
Adds a velocity-gated pointer barrier, events to notify a client when barriers
are hit, and a mechanism for clients to temporarily allow movement through
a barrier.
Signed-off-by: Christopher James Halse Rogers
christopher.halse.rog
Halse Rogers r...@ubuntu.com Wed, 25 Jan 2012 14:42:06 +1100
+
+libxfixes (1:5.0-6~hacking1) precise; urgency=low
+
+ * More and different thresholding
+
+ -- Christopher James Halse Rogers r...@ubuntu.com Wed, 25 Jan 2012 11:56:16 +1100
+
+libxfixes (1:5.0-5) precise; urgency=low
+
+ * Pointer
From: Christopher James Halse Rogers christopher.halse.rog...@canonical.com
Adds a velocity-gated pointer barrier, events to notify a client when barriers
are hit, and a mechanism for clients to temporarily allow movement through
a barrier.
Signed-off-by: Christopher James Halse Rogers
runs
into roundtrip latency, and there's some useful information that the server
has that's not easily available to a client.
This is the second go at a protocol. The first simply added a velocity-gated
pointer barrier request. In testing this suboptimal behaviour - getting the
pointer past
40 matches
Mail list logo
