Leo does not display all content of a node ...

[Viktor Ransmayr]

Hello Edward,

even at the latest revision (rev. 5500) Leo does not display all content of larger nodes
- Larger nodes approximately defined as >= 150 lines ...

That is searching for example for a 'TO-DO' item just return this particular line w/o the
context  around. - Going up - or - down does not refresh the screen & content ...

I thought I could provide you with an outline, where this problem consistently shows up.
- However, whenever I trim the personal outline I'm using the problem disappears.

This problem is really annoying - and - I would gladly provide more input, but so far I
fail. - Any suggestion?

With kind regards,

Viktor

PS: For completeness here's the log from Leo's startup:

<log>

Leo Log Window
Leo 4.11 devel, build 5500, 2012-10-19 18:35:23
Python 3.2.2, qt version 4.8.0
Windows 6, 1, 7601, 2, Service Pack 1
leoID=VR20100603 (in D:\Users\Viktor Ransmayr\.leo)
load dir: D:\Branches\leo-editor\leo\core
global config dir: D:\Branches\leo-editor\leo\config
home dir: D:\Users\Viktor Ransmayr
reading settings in D:\Branches\leo-editor\leo\config\leoSettings.leo
reading settings in D:\Users\Viktor Ransmayr\.leo\myLeoSettings.leo
reading settings in D:\Users\Viktor Ransmayr\Documents\Leo-BR-r5500.leo
reading: D:\Users\Viktor Ransmayr\Documents\Leo-BR-r5500.leo

</log>

[Terry Brown]

On Sat, 20 Oct 2012 05:28:56 -0700 (PDT)
Viktor Ransmayr <viktor....@gmail.com> wrote:

> even at the latest revision (rev. 5500) Leo does not display all content of
> larger nodes
> - Larger nodes approximately defined as >= 150 lines ...
>
> That is searching for example for a 'TO-DO' item just return this
> particular line w/o the
> context around. - Going up - or - down does not refresh the screen &
> content ...

I can confirm that this type of bug is still present in 5500 also.

Yesterday I was noticing this:

- editing a node (A)
- create new node by accidentally hitting insert
- delete new node immediately while still in headline edit mode using
cut-node
- node A is displayed incorrectly, a line is missing, selecting the
body restores the missing line

vs. the above but selecting the body of the inserted node, then
deleting it, in which case A is displayed correctly without selecting
its body.

Today (the outline's changed) it's not doing that, but I still
notice the difference between inserting and immediately deleting a node
(scroll position in A restored incorrectly), vs. inserting a node,
selecting its body, and then deleting it (scroll position in A restored
correctly).

So, there's some execution path difference between A being selected
after an inserted node is deleted immediately (still in headline edit
mode) vs. after selection of its body.

Not a very helpful report, but maybe the difference between deletion of
the node immediately and after selecting its body guides you to a
particular piece of code.

Cheers -Terry

[resi147]

Hi,

I also have the same problem, using the official 4.10 final.
I.e. a couple of lines are missing in the node (the linecounter
increments and decrements but the cursor does not move).

Not sure what report could be useful.
I also feel like it occurs on larger body nodes.

Cheers,
Karl.

[lewis]

Hi,

Same issue for me has been occurring on a large node. Interestingly, I can only reproduce the display error when 'Leo Log Window' is at bottom left position which is my ''initial_split_orientation' setting (horizontal: body pane to the right).
I can use Window>Toggle Split Direction to correct the initial display error.

For me, the display error always becomes evident at line 95.
My line numbers 95,96 are visible then skips to 118. Lines 97 thru 117 are not displayed.
It appears to be graphics performance time lag; if I return to the file after having switched to another leo tab the previously invisible lines are visible.

Leo Log Window
Leo 4.11 devel, build 5647, 2013-04-02 08:03:37
Python 3.3.1, qt version 4.8.4

Windows 6, 1, 7601, 2, Service Pack 1

Regards
Lewis

[Edward K. Ream]

Terry, could you please file a bug report?  Thanks.

Edward

[Terry Brown]

On Wed, 1 May 2013 03:23:46 -0500
"Edward K. Ream" <edre...@gmail.com> wrote:

> > Today (the outline's changed) it's not doing that, but I still
> > notice the difference between inserting and immediately deleting a node
> > (scroll position in A restored incorrectly), vs. inserting a node,
> > selecting its body, and then deleting it (scroll position in A restored
> > correctly).

> Terry, could you please file a bug report? Thanks.

Although I still see the above behavior in my personal set up, I can't
reproduce in vanilla Leo. I'll post a bug if I get something
reproducible.

Cheers -Terry

[Edward K. Ream]

On Wed, May 1, 2013 at 8:36 AM, Terry Brown <terry_...@yahoo.com> wrote:

Although I still see the above behavior in my personal set up, I can't
reproduce in vanilla Leo.  I'll post a bug if I get something
reproducible.

Thanks.  I've just created a to-do item to reopen the old bug.  Yesterday I read an email relating to this.  I'll attempt to find it and add it to the report.

Edward