my apologies for the late answer to this whole thing, but this is sort-of a
reply to all three emails by you guys.
On Tue, Jan 19, 2010 at 01:00:27PM +0100, Simon Thum wrote:
> Bradley T. Hughes wrote:
> > On 01/18/2010 11:54 PM, ext Carsten Haitzler (The Rasterman) wrote:
> >> hey guys (sorry for
On Thu, Feb 04, 2010 at 10:33:14AM +0100, Benjamin Tissoires wrote:
> Thoses definitions have been included in the kernel but the X server is not
> updated accordingly.
> Without these definitions, the multitouch axes are not correctly labelled.
>
> Kernel 2.6.33-rc6 and above also declare ABS_MT
Daniel Stone пишет:
>
> The filter should get called for _any_ key press and release. So you
> get Ctrl+Shift and set the flag in the filter private. Then someone
> presses, say, B, which should cause the very same filter handler to get
> called _again_. You notice it's another keypress, and cl
On Fri, Feb 05, 2010 at 01:58:33PM +0100, Julien Cristau wrote:
> That commit created a single ext_handlers[] array to check for
> non-overlapping extension events, but the event codes need to be
> per-display, so checking them globally is wrong.
>
> This reverts commit 83fdb27df4ddc2fb088ddf2ec65
This makes editing flags less error-prone.
It also changes the types of the affected masks to the type of its
component-flags. To be consistent it adapts the type of related flags
where appropriate.
Signed-off-by: Dirk Wallenstein
---
Diff to v1 is that the types of related masks are changed, to
On Sat, Feb 6, 2010 at 17:01:51 -0500, Gaetan Nadon wrote:
> Currently, the code is extracted from git, and when built with linuxdoc,
> a new dmx.txt is created and overwrites the one from git. Running 'make
> clean' removes the dmx.txt and now git thinks the file is deleted. If
> you try to pull