On Oct 28, 7:35 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> The only items on the urgent to-do list involve key handling. This is > tricky and may take several hours. OMG, what an understatement. Rev 1410 now contains the expected keyboard-dependent hack that handles Qt keystrokes such as Control- Shift-0. The problem is a mismatch between the information that Qt supplies and the Tk-oriented bindings used in leoSettings.leo. In this case, the qt plugin must match Control-Shift-0 with Ctrl-parenright. The horrors are contained in tkKey and especially the shifted method and its two keyboard-related helpers. We *might* be able to ignore the keyboard dependency for some time, but I think it will ultimately bite us. As mentioned in another post there are workarounds, which can now be adapted to apply directly to the two helpers: keyboardUpper1 and keyboardUpperLong. Ultimately, the solution will be to express Leo key bindings in a way that can be associated directly with Qt key events. However, this can't be done easily, as it would imply major changes to exquisitely delicate code in Leo's core, and these changes would, naturally, affect the present Tk bindings. But let's not dwell on the down side :-) Right now Leo looks like it handles all keys properly, at least on my keyboard... Much more testing is needed. Any reports of key-related problems are now welcome. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
