|
Post by George on Mar 29, 2022 13:00:52 GMT -5
Robert: It seems that R-CTL and any numeric key generates the X'00' character.
Can't tell from the code, but uncommenting some old DEBUG output, it looks like I see the R-Ctl go down, then the nueric key and then the reverse as they go up.
So for R-Ctl-2 I only see a Keycode/Scancode of 32/20, not 32/03.
As you are aware, debugging in the KB trap is extremely difficult, but if this is just to try and provide for entering a true NULL (X'00') character, why would we bother? Who actually wants to TYPE a NULL character?
If R-Ctl-(numeric) is supposed to be a NULL, then why doesn't any normal KB entry program support it?
Or is this just a 'curiosity' question?
George
|
|
|
Post by George on Mar 30, 2022 8:56:20 GMT -5
Robert: If I set Ctl-2 to (Passthru), the keystroke is passed to the MS API ToAsciiEx function. I debugged it and it returns a 0 (zero) RC which is described as "The specified virtual key has no translation for the current state of the keyboard.".
The keyboard routine then correctly ignores the keystroke.
So if the normal API can't figure it out, it's ignored.
George
|
|
|
Post by George on Mar 30, 2022 9:57:17 GMT -5
No problem checking it. It gets very busy in there with all the Up/Down key notifications. It amazes me that keyboards work at all.
George
|
|