[Bug-xnee] Re: xnee bug -- extra keydown leaving x in a strange state

[Henrik Sandklef]

Hi!

 Enough is enough .... it's about time we fix this :(

 Thanks for the script. It will patch a fault in Xnee. But a solution is
on its way (actually tested right now!).

 When stoppping Xnee using Ctrl-C (causing a sig) or key+modifier Xnee
must make sure that the keys used to stop Xnee is not recorded since only
the key presses will saved and the key releases will be sent from the
sever after Xnee has stopped and therefore not end up being recorded. I
wrote some code handling key+modifier that I actually got working. But I
figure this is error prune so I removed it.

 In the coming version of Xnee there is fewer supported ways of stopping
Xnee:
   - Using an "Xnee action key".
       For example you can make Xnee stop recording when pressing F1
   - Setting a time limit
   - Setting the amount of data to record

 Unsupported ways of stopping Xnee:
    - SIGNAL way of stopping Xnee

 Removed ways of stopping Xnee:
    - modifier+key is removed completely
        ... allthough I liked the solution from a technical
        point of view, but not when thinking of maintaining it ;)



 ..... I am (constantly) lacking the time to test the new features in
Xnee, but hopefully there will be a "test" version coming out soon.


Beat regards, hesa



> Hi, I was having the same problem that Rob described in the post:
>
> http://mail.gnu.org/archive/html/bug-xnee/2004-03/msg00003.html
>
> I wrote a quick python script to post-process the .xnl files and remove
> the offending keydown(s).
>
> Hope it helps...
>
> Josh


-- 
Though we rush ahead to save our time
We are only what we feel

 -- Neil Young / On the Way Home --