My issue is that we migh be introducing some new code here without having them mean anything anywhere else…

Yes. It would be better if we had access to both the "keysym" and the "keycode" in the Smalltalk image. Unfortunately, there is only a single value reserved for this in our event structure. So, we have to merge both value ranges in a meaningful way. I just did that. You can restore the "keysym" in the image by setting 0xff__ again.

Do you have a better Idea on merging "keysym" (special keys and alpha-num latin-1) and "keycode" (for shifted alpha-num keys) into a single value? That single-byte lookup table in Squeak is quite handy ... and fast. :-) And what the other two platforms provide.

Also, what does "virtual" mean here? are we trying to map to the thing printed on the keyborard or to the position of the key pressed?

The concept stems from the MSDN documentation. I elaborated on this topic several times on squeak-dev already:

• http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-April/215203.html
• http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-April/215208.html

The code reads xkey2sqVirtualKeyCode, which clarifies its meaning within the Smalltalk image.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.