"AIS, Informofico" <i...@ais-sanmarino.org> wrote:

Hi,

> "let me know when the fix goes from "candidate" to "actually
> fixes the problem" :)"
>
> As the author of the patch I regret to say that it is not
> likely to fix this problem.

Yeah. Besides removing "magic values" and replacing them with proper
definitions, it doesn't do much.

> The problem addressed by the patch was an environment (hardware?
> software?) that delivered GTK mouse events with an extra bit (0x2000)
> set. This caused ALL processing of mouse events to fail. In the

I'd really like to understand why this happened. The events were
filtered by the lock masks (numlock etc) that you removed, so I'd really
like to know what's happening on your end that doesn't happen everywhere
else. (and I'd also need to look at the code to understand why the masks
are here in the first place)

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <jbla...@debian.org> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to