I fixed this by going to leoGuiPluginsRef.leo -> Qt gui -> class
leoQtEventFilter and modifying the special map like so:

    special = {
        'Backspace':'BackSpace',
        'Esc':'Escape',
        'Del':'Delete',
        'Ins':'Insert',
        'PgDown':'PgDn',
        'PgUp':'PgUp'
    }

Note that 'PgUp' is mapped to itself.  If it's not there, the ignore
flag gets set to true.  I guess all of the toString values for the
control chars have to appear in the special map since there is no
associated char?  Or maybe that's a bug with the method logic...
Anyway, there you go.

On Jan 23, 4:03 pm, Jesse Aldridge <[email protected]> wrote:
> PgUp and PgDn seem to have a related problem; if I rebind them to
> something else, they are still bound to page up and page down.
>
> I also tried binding the insert key, but I'm not sure if that one's
> valid.
>
> It would be nice if leo printed an error message on an unrecognized
> key-binding.  Right now I can change: "delete-char = Delete" to
> "delete-char = FredFlinstone", and leo reports no error (and
> interestingly, the delete key still deletes a character).
>
> In case your wondering why I'm messing with all these keys, it's
> because I'm used to Freemind.  In Freemind, "insert" inserts a child
> node, "return" adds a sibling node, "delete" deletes a node, and the
> arrow keys move around.  It's nice because all those keys are located
> on the right side of the keyboard so you can easily navigate the nodes
> with just your right hand, and you don't have to take your left off
> the home row.
>
> Home, end, and backspace are working for me, so I think I'll just go
> ahead and use them instead.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to