[squeak-dev] Unix keyboard events lose track when multiple keys pressed or keys held down

tim Rowledge tim at rowledge.org
Sun Jan 17 19:07:52 UTC 2021



> On 2021-01-17, at 1:47 AM, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
> 
> IMO it's a mistake: we should always pass the keypress/release events as is to the image, that's what raw events means to be. Composition shall alter the keychar events only - that is some 1st level interpretation of the raw events...

I have much sympathy with this idea and some past experience with using it.

The good part is that you get the raw input and can do whatever you want with it; the bad part is that you get the raw input and *have* to do something with it! That can cost so much effort that you just fail to provide the user with what is needed.

In this case it would be converting the raw key code to characters with a map; but we'd have to work out how to build the map for each platform, for each variety of keyboard (Aaargh! Dvorak user approaching! Run away!) and each language. I don't think I'll live long enough to be able to implement that.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: JSP: Jump on Sexy Programmer




More information about the Squeak-dev mailing list