On Tue, Aug 12, 2014 at 10:03 AM, jkn <[email protected]> wrote:
> some of the most IMO convenient key-bindings in Brief need some special > effort before they can work in Leo. For instance: > > 1) The numeric key-pad keys are used for special purposes > 1a) <keypad-minus> is cut (region if selected, else current line) > 1b) <keypad-plus> is copy (region if selected, else current line) > 1c) <keypad-insert> is insert from clipboard > This works brilliantly, but would require some Qt KeyHandler work to > disambiguate the numeric keypad keys from the 'standard' plus, minus, insert > keys > > 2) the use of multiple presses of <home> and <end> > 2a) a single <home> moves the cursor to the beginning of the current line > 2b) a double <home><home> moves the cursor to the top of the current page > (as viewed) > 2b) a triple <home><home><home> moves the cursor to the top of the current > buffer (would correspond to outline, I guess) > Similarly for multiple presses of <end> Interesting. I don't remember, if I ever knew, how Qt handles double/triple key presses. As you probably know, key handling in Leo (and really, everywhere) is fraught with complexities. That's not going to change any time soon. There are two places to start any investigation of keystrokes in Leo: k.masterKeyHandler and LeoQtEventFilter.eventFiler. Both contain many tracing options. In particular, eventFilter and it's helpers can trace whatever events Qt is generating. Understanding what events Leo actually gets is the first step. Be sure to check out LeoQtEventFilter.traceEvent. It can be your friend. HTH. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
