Freaky [caps/num] lock key behaviour

Two questions, related to the fact that these keys do not generate keyup
events :

  1. will there be an option to make these just act like regular keys in the
    future (I’d rather not support my own source modification if possible),

  2. for what reason is it useful not to generate keyup events for these keys?
    I just can’t figure it out, and I’d really like to know. And why is scroll
    lock exempt?

-Thomas

  1. will there be an option to make these just act like regular keys in the
    future (I’d rather not support my own source modification if possible),

the intention is probably to make SDL’s internally kept key state
reflect the locking state of these keys rather then their up/down state.
I’d say it’s a bug, and I wouldn’t mind changing it if it doesn’t break
too much

Even so it’s unwise to rely on the precise behaviour of these
keys; some X servers (XSun) suppresses the keydown event when a locking
key is toggled on, and the keyup event when it’s toggled off

I could be mixing things up here, but from what I remember of talking
directly to PC keyboards, this is actually what you get from those
keys; only one event per key down+up. This may be configurable by
sending some commands to the keyboard MCU, though…

//David

.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------> http://www.linuxaudiodev.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |--------------------------------------> david at linuxdj.com -'On Friday 13 April 2001 13:31, Mattias Engdeg?rd wrote:

  1. will there be an option to make these just act like regular
    keys in the future (I’d rather not support my own source
    modification if possible),

the intention is probably to make SDL’s internally kept key state
reflect the locking state of these keys rather then their up/down
state. I’d say it’s a bug, and I wouldn’t mind changing it if it
doesn’t break too much