thank you, this does help.
When clicking with no modifiers, two button-ups are sent:
T{ button-up { # 1 } }
T{ button-up }
When click with most modifiers (here control), three button ups are sent:
T{ button-down { mods { C+ } } { # 1 } }
T{ button-down { # 3 } }
T{ button-down }
But when clicking with the shift key, that last, generic button-up is never
sent:
T{ button-up { mods { S+ } } { # 1 } }
T{ button-up { mods { S+ } } }
Is this intentional, or is this something I should fix?
Doug Coleman wrote:
> Sam,
>
> Try running "gesture-logger" run in the UI.
>
> The black window captures keyboard and mouse gestures to the white
> logging window. That should help you debug things.
>
> Doug
>
> On May 14, 2009, at 9:23 AM, [email protected] wrote:
>
>> For some reason, the button-up handler isn't getting called on a
>> shift click. I
>> could fix it by manually calling the handler after a button-down,
>> but it seems I
>> shouldn't have to. Am I doing something wrong with command maps
>> (where is
>> sundry defined?) or is this a bug with the gestures vocab?
>>
>> Ben Schlingelhof wrote:
>>> Great, lovely, phantastic. Just what I needed. One thing though: the
>>> selected-values model gets updated when I command-click, but not when
>>> I shift-click (Mac). Apart from that I love it. Thanks.
>>>
>>> Ben
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
