On Saturday, April 14, 2018 at 6:06:05 AM UTC-5, Edward K. Ream wrote:
This post discusses my present thinking about key handling.
>
The project is going well. My recent cff studies have given me a deep
knowledge of what needs to be done.
I am proceeding methodically: Investigate using cff, mak
On Sat, Apr 14, 2018 at 1:48 PM, Terry Brown wrote:
TypeError: toStroke() takes 2 positional arguments but 3 were given
>
My apologies to all. This was an artifact of merging the new eventFilter
code into devel.
pylint caught this a bit later, after you did. I'm running pylint a lot
these day
One other condition that causes the traceback.
Touching the any key while the insertion point is in the find
dialogue, whether it has been filled via the behaviour described above
or if it contain only the "find pattern here" string that you get when
the body has no text.
So basically the only ti
Find dialogue = The actual box to type in or where the selected string
is placed.
Find tab = The UI element that is selectable by clicking on it while
the log pane is being the log.
Find pane = The pane that holds the find dialogue and search options.
plo.litcn^ftuwsf]sd;f"
Place the insertio
Using backspace or delete to clear the contents of the find dialogue
of the selected words produces the traceback:
Traceback (most recent call last):
File "/home/chris/leo-editor/leo/plugins/qt_frame.py", line 813, in wrapper
return self.keyPress(event)
File "/home/chris/leo-editor/leo/plu
I am also using aa23ac452c9f.
But the Ctrl-F behaviour I am seeing (last couple of comments on #794,
post fix) started with 0d125d52483e, the fix for #794.
As I was fiddling with the Find pane:
Traceback (most recent call last):
File "/home/chris/leo-editor/leo/plugins/qt_frame.py", line 813
On Sat, 14 Apr 2018 13:47:46 -0500
Terry Brown wrote:
> Ctrl-F seems broken in aa23ac452c9f, I was thinking this was related
> to the #794 but now realize it's probably the new key handling code.
> Focus looks right, but nothing I can do (click, select, whatever)
> let's me type content in the Fi
Ctrl-F seems broken in aa23ac452c9f, I was thinking this was related to
the #794 but now realize it's probably the new key handling code.
Focus looks right, but nothing I can do (click, select, whatever) let's
me type content in the Find: field.
Cheers -Terry
--
You received this message because
Hi Edward
On Saturday, April 14, 2018 at 12:06:05 PM UTC+1, Edward K. Ream wrote:
>
> This post discusses my present thinking about key handling.
>
> I have abandoned the keys branch and created a new keys2 branch. The
> keys2 branch is a clean start, based on devel. The only survivor from the
This post discusses my present thinking about key handling.
I have abandoned the keys branch and created a new keys2 branch. The keys2
branch is a clean start, based on devel. The only survivor from the keys
branch is a simplified eventFilter that should work *exactly* as before.
That code ha
10 matches
Mail list logo
