On Fri, Nov 18, 2011 at 4:55 PM, SegundoBob <[email protected]> wrote:
> The problem with Alt+W is that it is the shortcut for the Windows menu. > You can replace the assignment of Alt+W that is in leoSettings.leo, > but that does you no good---unless there is some way I don't know to > turn off the menu shortcuts. That is, when I assign Alt+W in my > myLeoSettings.leo, Alt+W still just opens the Windows menu. Yes. This is a problem on Windows; it is a much bigger problem on MacOs. > This makes me wonder if the assignment in leoSettings.leo of Alt+W to > propogate-key-event was ever effective or useful? The intent of propogate-key-event is to force the key to be passed on to the OS. Recent changes may have broken this behavior. What *used* to happen was that k.masterKeyHandler (via its helpers) would return a flag indicating whether Leo had completely handled the key stroke. Recently, I "improved" the code by having k.masterKeyHandler not returning anything (to eventFilter). This was supposed to simplify the interface, and it does, but as I write this I realize Leo probably needs some special-case code to handle propagate-key-event. I've just put it on the list. Edward P.S. Iirc, Ctrl-Q is the default binding that closes a *tab* with the qttabs gui. I dislike this binding, and would prefer Ctrl-W, but Ctrl-W is the long-time binding to select-word, so I don't want to change the default. Actually, I don't even change Ctrl-W in my copy of myLeoSettings.leo, because it is so useful. So I just live with Ctrl-Q ;-) EKR -- 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.
