From: Hugues B. <non...@gm...> - 2011-02-07 08:21:09
|
> gdk_keyval_name() and gdk_keyval_from_name(), equivalent to Xlib's > XKeysymToString() and XStringToKeysym(). Qt doesn't seem to include > anything analogous. How would a normal Qt program be expected to > handle it? QKeySequence::fromString could probably be coerced into doing that even though this is not its primary purpose. > Interesting point, I didn't think about having multiple concurrent > keypresses. That sounds like a fine format to me. Should there be > implicit pauses? Certainly in "Alpha,Alpha,Math" there needs to be a > pause between presses of Alpha, but not necessarily between pressing > Alpha and Math. What's important is not so much a pause but a duration for each key press to make sure it is caught by the OS or the program currently running. Successive keys also shouldn't overlap to avoid misunderstandings when programs use direct input. > Do you think it's really necessary to handle sequences of (PC) keys? > I'd rather keep it simple. Not strictly necessary but : * why not make it general if it doesn't require extra work? * Qt (via QKeySequence) allow for such sequences (up to 4 consecutive key events) * as strange as it may seem, some people actually expect them (emacs user for instance though they are probably not over-represented in the TI community...) > Keep it simple? Make sure the timing is such that it works with > GetCSC, and isn't too painfully slow. Sure. It's been a while since I last looked into tilem and tios internals so I have no idea what a good delay would be and I'm not exactly sure what's the best way to enforce it. A timer in the gui thread might do the trick but it may not be very accurate... > I suppose you're right, but I don't see that being an issue for normal > users. > Calculator keypads don't like having lots of keys pressed at once, either. It's my understanding than with direct input they can handle a lot more simultaneous keypresses than a PS/2 keyboard can. More importantly the issue is that if you bind CTRL+X to calc key A and CTRL+Y to calc key B pressing CTRL+X+Y probably won't simulate pressing A+B (unless some dirty hacks are used) > We also don't really have any keys to spare on a normal PC keyboard. Well, it doesn't have to be a keyboard modifier, it could just as well be a button on the UI or another keypress that toggle between "normal" and "persistent" calc keypresses. Hugues |