I think it makes perfect sense to not parse bindings "partially", so that you see 0 instead of ). If tk does that, i would say it is broken instead.
On 4/8/09, Edward K. Ream <[email protected]> wrote: > > > > On Apr 7, 2:07 pm, "Edward K. Ream" <[email protected]> wrote: > >> > That is, it would seem to be possible to avoid the horrible, keyboard- >> > dependent "shift", "keyboardUpper1" and "keyboardUpperLong". > > Drat. There is a big glitch. On my keyboard, Qt reports Shift-0 as > '(', but reports Ctrl-Shift-0 as Ctrl-Shift-0 (!!) > > My plan is to keep the new, simpler code, but to build in some more > capabilities. These are not strictly necessary. One could require > the user to bind commands to Ctrl-Shift-0 instead of Ctrl-( or Ctrl- > parenleft, but that's ugly and might lead to different bindings for Qt > and Tk. > > So some new invention is needed--perhaps an *optional* description of > keyboard layout. I'll sleep on this... > > Edward > > > -- Sent from Gmail for mobile | mobile.google.com Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
