I confirm the same behavior on Windows 10, latest development build of 64-bit
Factor.
It doesn't depend on the numpad or on physical keys.
For example, when I use the normal English/US layout, the keys for semicolon
and comma (";" and ",") generate only the "key-down" events. Pressing "q" and
"w" generates both "key-down" and "key-up".
If I switch to the Programmer Dvorak layout, the physical keys that used to be
"q" and "w" in the US layout now will produce the ";" and "," correspondingly,
and they will again produce only the "key-down" events in the gesture-logger.
Pressing the keys that formerly produced only "key-downs" as ";" and "," will
now produce both "key-down" and "key-up", being mapped to "s" and "w".
It seems that the physical keyboard or the layout is not to blame. For some
reason Factor eats some of the key-up events for punctuation characters.
There are many such characters that I can see treated differently by Factor:
#&$^-=\`:;~/'"?@_[]{}(*+
These Factor's treatment of these keys is not dependent on the physical key,
but on the logically mapped character it produces under the currently selected
layout.
Numpad keys may be different in that even when Programmer Dvorak produces
"a"-"f" or "x", they still don't give a ""key-up" event.
09.03.2019, 09:08, "John Benediktsson" :
> Interesting! Okay.
>
> Any details of the keyboard type or language settings you can share? Windows
> 7? Is it 32-bit or 64-bit Factor?
>
> Thanks,
> John.
>
> On Mar 8, 2019, at 8:26 PM, KUSUMOTO Norio wrote:
>
>>> 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.
>>
>> Normal minus, dot, comma, colon, semi-colon key are also similar.
>> There are not notifications about key-up.
>>
>> --
>> KUSUMOTO Norio
>>
>>> 2019/03/09 13:00、KUSUMOTO Norio のメール：
>>>
>>> Hi,
>>>
2019/03/09 10:02、John Benediktsson のメール：
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.
>>
>> ___
>> Factor-talk mailing list
>> Factor-talk@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
> ___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
---=---
Александр
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
