I'd like to fix all the rough spots in Leo's Qt gui code this week.

Two bugs have already been fixed:

1. Can't enter text directly in the Find panel:
https://bugs.launchpad.net/leo-editor/+bug/783617

After experimentation I have chosen simply to disable the Find/Change
text areas so that they are merely status indicators.  Unlike the
check boxes, which *are* functional, it is basically pointless to type
text into these areas.  In the absence of buttons that would execute
various find/change commands, the user must *still* do Ctrl-F.

BTW, the Tk Text boxes *are* functional, in the sense that they do
update the default find/change strings when the user types text into
them.  However, to make this work, any in-progress minibuffer command
must be aborted, so once again typing into these boxes is pointless.

In other words, the Tk code should work like the Qt code.  I'm not
going to do this because the Tk code is on its way out.

Happily, Leo's core remained unchanged.  This is important because the
Qt code is horribly complex.  After Tk is gone, significant
simplifications can be made.  But I'm not going to do that now...

2. Shift-Delete not working in Qt
https://bugs.launchpad.net/leo-editor/+bug/681797

Fixing this bug was trivial.  I finally realized why I was reluctant
to allow Shift modifiers for keys like Delete, Backspace, Insert and F-
Keys.  Without bindings, typing these characters inserts strange
character.  Doh!  All I had to do was to add default bindings for
these keys in leoSettings.leo.

Both these bugs should have been fixed a year or two ago.  Ditto for
the remaining bugs:

leo overrides minibuffer background color
https://bugs.launchpad.net/leo-editor/+bug/323967

Enter Headline Edit Mode when current node is the default
https://bugs.launchpad.net/leo-editor/+bug/701188

Shortcuts don't work in most Log frame tabs
https://bugs.launchpad.net/leo-editor/+bug/701261

rst 3 button in contextmenu throws an error
https://bugs.launchpad.net/leo-editor/+bug/751976

viewrendered.py behaviour
https://bugs.launchpad.net/leo-editor/+bug/755206

fill-para doesn't respect setting from set-fill-column
https://bugs.launchpad.net/leo-editor/+bug/766747

PgUp/PgDown should scroll the body, not the tree
https://bugs.launchpad.net/leo-editor/+bug/394309

Most of these are straightforward to fix.  I'd like to get them all
done in about a week.

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.

Reply via email to