Hi,
I'm currently in the process of updating my gesture-recognition
application easystroke to reflect the XInput changes in xserver-1.6 and
I have a couple of questions about the direction that we're headed.
The first question is about the behavior under core pointer freezes
caused by passive
Daniel Stone wrote:
On Thu, Dec 11, 2008 at 11:32:57AM -0500, Thomas Jaeger wrote:
I'm currently in the process of updating my gesture-recognition
application easystroke to reflect the XInput changes in xserver-1.6 and
I have a couple of questions about the direction that we're headed
You really need the glyph cache in the X server to get decent text
performance out of the 2.5 intel driver. The patches are pretty
straightforward to backport, but it is my understanding that a 1.6
server will be uploaded to jaunty soon, so you might want to wait for that.
Jeffrey W. Baker
00:00:00 2001
From: Thomas Jaeger thjae...@gmail.com
Date: Sat, 20 Dec 2008 16:17:02 +0100
Subject: [PATCH] Don't release grabs unless all buttons are up
Previously, only buttons = 5 would count here.
---
Xi/exevents.c |2 +-
dix/events.c |2 +-
2 files changed, 2 insertions(+), 2
function AllButtonsAreUp.
Thanks,
Tom
Thomas Jaeger wrote:
I can't see any reason why we would treat buttons 5 differently. This
patch simplifies client code by eliminating the need to call XGrabDevice
after a button has been pressed and prevents race conditions that could
result from
sense for buttonsDown to count the number of buttons
that are down and aren't mapped to 0. I hope I'm not way off.
Thanks,
Tom
Thomas Jaeger wrote:
This turned out to be a little bit trickier than I initially thought,
since buttonsDown counts the number of physical buttons that are down,
before
The attached patch implements the suggested behavior. I don't think
that this violates the spec.
The question was actually about how the core pointer is reporting events
when they are being replayed after a grab by a different client. Here
is a part of the xev output in this situation:
Using the latest xserver from server-1.6 branch, when
XTestFakeRelativeMotionEvent is called with a delay parameter !=
CurrentTime, the client may crash under certain circumstances. I've
also seen problems with the same symptons on earlier X servers, but I've
never been able to reproduce them.
http://cgit.freedesktop.org/xorg/xserver/commit/?id=d21155a3e9b51df946766926bc6155c8972c4439
Here's the correct link to the thread where this was previously discussed:
http://lists.freedesktop.org/archives/xorg/2008-June/035943.html
In current X servers, the button field is a bit mask, so
Sorry, forgot the attachment.
Thomas Jaeger wrote:
The attached patch implements the suggested behavior. I don't think
that this violates the spec.
From c41b2dcfe145022b1a3dba4243ad992e903238f2 Mon Sep 17 00:00:00 2001
From: Thomas Jaeger thjae...@gmail.com
Date: Sat, 3 Jan 2009 17:19:55 -0500
I think the current behavior violates the core spec: If, say, button 1
is pressed on a device where it is currently disabled, but it is mapped
to itself on the VCP, then an XSetPointerMapping request that doesn't
change the mapping of button 1 will nonetheless fail.
Thomas Jaeger wrote
Are you running the tip of xserver-1.6 branch? Specifically, do you
have this patch applied?
http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branchid=0d12c44d832b98da10dccc3b8bac7676d8ea2c96
The patch fixed a similar issue for me [1]. The problem persists in
connection with
Alexia: What is the point of remapping buttons willy-nilly before
posting an event anyway? The comment suggests it just servers as a
reminder of how remapping works. It's problematic in that proper
DeviceMappingNotify events aren't send and I don't want to think about
what could potentially
Peter Hutterer wrote:
On Thu, Jan 08, 2009 at 01:43:39AM -0500, Thomas Jaeger wrote:
Alexia: What is the point of remapping buttons willy-nilly before
posting an event anyway? The comment suggests it just servers as a
reminder of how remapping works. It's problematic in that proper
What is it exactly that you want to do? If you just want to be notified
of key presses, all you have to do is grab the key on all the extended
input devices. In xserver 1.6, if you also want applications not to
receive the events, you can change the core pointer mapping. If I
understood Peter
Patrick Sebastian Zimmermann wrote:
I want that a chosen application (in my case a hotkey daemon) receives
all input device events even when they are grabbed by other
applications. Even though I don't yet know the X internals, I guess
this is not done by simply grabbing all input devices. This
Thomas Jaeger wrote:
Using the latest xserver from server-1.6 branch, when
XTestFakeRelativeMotionEvent is called with a delay parameter !=
CurrentTime, the client may crash under certain circumstances. I've
also seen problems with the same symptons on earlier X servers, but I've
never been
this, I'm inclined to just leave the device button map
alone and handle all the remapping in the driver (see the attached patch).
From d760878f4c74a52467b0b9d5e4ac0ba0af4e583f Mon Sep 17 00:00:00 2001
From: Thomas Jaeger thjae...@gmail.com
Date: Fri, 9 Jan 2009 14:08:20 -0500
Subject: [PATCH] Don't touch
Peter Hutterer wrote:
On Mon, Jan 05, 2009 at 11:55:40AM -0500, Thomas Jaeger wrote:
From 3f8ba578ad18b7135031197f6ec5145afcd1479a Mon Sep 17 00:00:00 2001
From: Thomas Jaeger thjae...@gmail.com
Date: Mon, 22 Dec 2008 00:55:09 +0100
Subject: [PATCH] Count the number of logically down buttons
for EXTEND_PAD can hopefully disabled someday. It'd be nice if someone
with git access could commit this patch.
Thanks,
Tom
From e2536dac06d82f2d2a2b77d8d00fc85925889d81 Mon Sep 17 00:00:00 2001
From: Thomas Jaeger thjae...@gmail.com
Date: Fri, 30 Jan 2009 16:25:07 -0500
Subject: [PATCH] CheckComposite
Alexei Babich wrote:
Hello, all.
Having executed a piece of code listed below, I get a green window (as a
result of calling XCreateSimpleWindow()) and a black rectangle on top of it
(XRenderFillRectangle()). I still get just black, whatever color I set in the
'col' structure.
Hi Peter,
Sorry for replying off-list first.
Thanks for the work you've put into this. I haven't spent a lot of time
testing the new code, but here are my first impressions. You're
probably aware of most of the issues below already, but I'll mention
them just in case.
* The biggest issue for
Thanks for the quick response.
Peter Hutterer wrote:
On Thu, May 28, 2009 at 02:54:22PM -0400, Thomas Jaeger wrote:
Thanks for the work you've put into this. I haven't spent a lot of time
testing the new code, but here are my first impressions. You're
probably aware of most of the issues
Soeren Sandmann wrote:
Thomas Jaeger thjae...@gmail.com writes:
An important question is when to use Render for Pad/Reflect (see the
commit message of the first patch), as we can't detect whether the X
server is using a broken driver and/or pixman version. I haven't
implemented any checks
* It seems to be pretty easy to crash the server using XI1 applications.
I'll provide more information later
Yes please. I'd need some sort of test-case to debug crashes.
Here's an easy to reproduce way to crash the server: Float the virtual
XTest core pointer (you can't do this
Peter Hutterer wrote:
* A driver sending a proximity event crashes the server.
Fixed, thanks. GetProximityEvents still had the valuator event calculation
in there and returned a wrong number of events. That, an an uninitialized
pointer that was only triggerd for proximity events. Both fixes
I've posted a build log (make -j4) here:
http://pastebin.com/f3f965926
The more I think about it, the more it becomes clear to me that a
recursive call to make can never do the right thing during a parallel build.
Tom
Dan Nicholson wrote:
On Tue, Jun 2, 2009 at 8:24 AM, Thomas Jaeger thjae
Peter Hutterer wrote:
On Tue, Jul 14, 2009 at 01:37:21PM -0700, Tyler McClung wrote:
Is there a way to hide the cursor on the fly without restarting the
server or window manager?
shouldn't XFixesHideCursor and XFixesShowCursor do the job?
(disclaimer: haven't actually used it)
On master,
You can (ab)use easystroke for this:
http://sourceforge.net/apps/trac/easystroke/wiki/TipsAndTricks
Tom
Johannes Truschnigg wrote:
Hello list,
what's today's preferred way of mapping keypress-sequences and -shortcuts
(like Ctrl+W, for instance) to buttons on a pointer device (e. g., my
here. Use the sysfs name attribute instead, which
does not suffer this problem. Fall back to the NAME property if the
attribute is not available.
Signed-off-by: Thomas Jaeger thjae...@gmail.com
---
config/udev.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/config
On 03/03/2010 07:48 PM, Dan Nicholson wrote:
On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger thjae...@gmail.com wrote:
The attribute 'name' might not exist (as in the case of serial wacom
devices) and it's impossible to set it in an udev rule, I believe, so we
should at least fall back
On 03/03/2010 08:25 PM, Dan Nicholson wrote:
On Wed, Mar 3, 2010 at 4:59 PM, Thomas Jaeger thjae...@gmail.com wrote:
On 03/03/2010 07:48 PM, Dan Nicholson wrote:
On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger thjae...@gmail.com wrote:
The attribute 'name' might not exist (as in the case
32 matches
Mail list logo
