Quoting Till Adam ([EMAIL PROTECTED]): > Hello all, > > I have been looking into fixing the fact that CAPS-Lock and NUM-Lock dont > work in DirectVNC and have a few questions. > > X appears to treat both num-lock and shift lock as modifier keys, while > dfb currently does not. This means that they are not part of the > modifier bitmap. Is this an oversight or is there a reason behind it? > > Also, I understand that while the shift key being pressed results in a > change of kb_table, caps-lock requires individual action depending on > the key being pressed (numbers remain numbers for example and are not > shifted). The question is, should this modification be done within DFB, > or should I modifiy the ascii values I get from dfb depending on the > state of the caps/num lock keys at the application level?
I think adding three modifiers and translating keys depending on them in the input driver (keyboard.c already does it for shift) is the right way. It should also handle keyboard LEDs. This way the app gets the *-lock press/release events and gets the proper key/ascii value with modifier bits for *-lock. > If you want me to, I can add the three modifier keys (num, caps, scroll) > and look into led handling. Go ahead if you agree or tell me what would be better for users/developers ;) -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" convergence integrated media GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
