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 clickin
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, anklesa...@gmail.com wrote:
> For some reason, the button-up handler isn't getting called
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?
Be
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
Table views can now have more than one selection. Modifiers are like those on
macosx: shift for selection up to a item, and command for arbitrary selection.
Pull changes at git://github.com/bogiebro/factor.git
--
The NEW
