On Sun, Nov 2, 2008 at 6:03 PM, Terry Brown <[EMAIL PROTECTED]> wrote:

>> It would be simpler and less bug-prone to
>> > just use the default qt functionality for headline editing, with the
>> > slight drawback that ctrl+a / ctrl+e would not work.
>
> Ctrl-I would also be lost, which I'd miss, although it's not a deal
> breaker.  But having to press 'Enter,Ctrl-I' to start a new node is not
> as fluid as just Ctrl-I.

Compromise is not an option.  The qt plugin must pass all unit tests,
and many of those test require full integration of headlines with
Leo's core.  This is the difference between prototype and finished
code.

At present, the difficulty is the handling of keystrokes during the
transition from focus in the tree or body to focus in the headline.
This exposes some 'infelicities' in the Qt key-handling events.

I suspect the solution is to abandon the headline hacks in
eventFilter.  The clean way to do this is to create a subclass of
leoQtEventFilter for headlines.  This may mean binding event filter
objects differently than at present.

Edward

P.S. Some patience would be helpful :-) Recall that it took me over a
year to integrate the minibuffer fully into Leo's core.  In the
process, almost all commands in leoEditCommands.py became
gui-independent.  The present headline work won't take that long, but
I *will* take the time to do the job properly.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to