On May 14, 2009, at 11:59 AM, [email protected] wrote: > 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?
I think that's just how Cocoa reports buttons. Ctrl+button is supposed to be equivalent to right-clicking, which is why you get two sets of gestures. I'm not sure what Cocoa event triggers the generic button-up/ down gestures, but it may be that holding Shift suppresses it. I noticed another oddity with keyboard gestures when holding down the Command modifier. You get a key-down event, but no key-up event. -Joe ------------------------------------------------------------------------------ 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
