Romain Robbes wrote:

> OK it works fine .... except maybe that the error messages
> are a bit obscure (The "duplicate entry" error message).
> For the sample example provided (m-8 t 1) I had to
> remove the previous m-8 binding, which seems fine
> but wasn't obvious.
>
> The second one (m-8 T 2) seems incorrect, as when
> I recapture it I get m-8 s-t 2. But I am unable to accept it either,
> due to the "duplicate entry" error message.
>
> So it is still a bit rough on the edges, but nonetheless quite 
> promising :-).
>
>     Romain
>

Thanks for the feedback.  I'll definitely improve the handling of 
duplicate entries and shifted keys in the next release.  Previously I 
didn't handle duplicates at all so my current sloppy hack is just there 
to prevent them.  As for the s-t vs T...this is a platform dependent 
issue which I am very interested in straightening out (some platforms 
don't list shift as a qualifier they just give the capital keycode, 
others include the shift qualifier and give a lowercase keycode).  What 
platform are you using?...just so I can add one more datapoint to my 
list.  Also, what does your platform report when you do something like 
meta-shift-2?  What about meta-shift-Insert (if your keyboard has such a 
key).  Your feedback is much appreciated.  Anyone else that wants to 
post some datapoints for me (platform and response to various shift, 
ctrl and meta-key combinations), that would be helpful as well.

David

-- 
C. David Shaffer
http://www.cs.westminster.edu/~shaffer
http://www.shaffer-consulting.com