Hi,
> 2019/03/09 10:02、John Benediktsson <mrj...@gmail.com> のメール：
>
> If you'd like to play around with how Factor receives various inputs,
> including the keyboard events, you can run the gesture-logger debug tool. It
> prints out a log of all gestures received by the window so you can see mouse
> movement, mouse clicks, key-up, key-down, etc:
>
> IN: scratchpad "gesture-logger” run
Oh, nice tool! I did it.
On my windows machine (Windows 7), when I hit 1 key which was in a separate
numeric pad,
Gesture log window showed :
T{ key-down { sym “1” } }
User input: 1
per one hit. The other hand, when I hit normal 1 key, it showed :
T{ key-down { sym “1” } }
User input: 1
T{ key-up { sym “1” } }
per one hit.
--
KUSUMOTO Norio
> 2019/03/09 10:02、John Benediktsson <mrj...@gmail.com> のメール：
>
> If you'd like to play around with how Factor receives various inputs,
> including the keyboard events, you can run the gesture-logger debug tool. It
> prints out a log of all gestures received by the window so you can see mouse
> movement, mouse clicks, key-up, key-down, etc:
>
> IN: scratchpad "gesture-logger" run
>
> I don't have a keyboard with a separate numeric pad with me to test, but I
> find that behavior odd. See if the gesture logger has the same behavior, and
> also, whether a key-up is ever generated for those keys. On some platforms,
> you might see several key-down before a key-up for repeated keys (like
> holding down a letter to type it several times).
>
> Best,
> John.
>
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
