Hacks like this seem quite untolerable. Perhaps we could have something in myLeoSettings.leo that checks for QKeyEvent::text(), and passes certain set of characters through as such. I originally suggested passing throuh whole ascii set, but it could just be a string with characters that user finds problematic.
----- Original message ----- > On Sat, Mar 6, 2010 at 2:54 PM, resi147 <[email protected]> wrote: > > Debugging leo with all the advice from Edward brought me to the > > conclusion that my problem has nothing to do with > > key/event handling. I think it is a very basic key bindings problem. > > The keys are all recognized correctly, i.e. > > The '@' is correctly reported as ALT-'L' in every of the mentioned > > functions. So my problem is, how to map the > > ALT-L to '@' in myLeoSettings.leo > > This must be done in qtGui.py, not in myLeoSettings.leo. > > The place for this kind of hack is in the class leoKeyEvent, after the > comment: > > # Last minute-munges to keysym. > > Something like this (not tested): > > if sys.platform.startswith('darwin'): > if tkKey == 'Alt-L': > tkKey = stroke = '@' > > Let me know exactly what works and I'll make the changes to the trunk. > > Edward > > -- > 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. > -- 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.
