I have done some more work to try to isolate the jump problem: I have created an outline with a single node. The node contains 146 lines. When one clicks anywhere at the end of the node it will always jump to line 145 as the last line shown (probably really line 144 since line 145 is slightly hidden at the bottom). One can add a few lines after line 144 without affecting the behavior. Before line 144 there are 858 characters. It doesn't matter what they are, but there must be at least 858 and must be before line 144. One can move the text around so long as these conditions are met the jump reliably happens. If one remove text so that there are fewer letters left, the jump go away. It doesn't matter where the node appears the above holds true. I have uploaded the file as an attachment to this post.
I am using: Leo Log Window Leo 4.11 devel, build 5418, 2012-07-04 02:53:55 -0500 Python 2.7.3, qt version 4.8.2 Windows 6, 1, 7601, 2, Service Pack 1 I don't use any private leoSettings. Body panel displays about 20 lines as default. I just noticed that the attached outline only display the jumping problem when the window is maximized. I believe that is because some of the long lines start folding back when I use the non max size. After I play around a bit to even out the longest lines I get the exactly same behavior as above whether my Leo window is maximized or not. I tried to look through the Leo code. I don't have enough high level understanding to locate where this could originate from. It is clear that line count and character count are both somehow involved. However the node position is not relevant. So my previous perception of a pattern there was probably just me being fooled by randomness. On Tuesday, July 17, 2012 11:09:21 AM UTC-7, Terry wrote: > > On Tue, 17 Jul 2012 10:49:11 -0700 (PDT) > "F.S." wrote: > > > Now sub node 8 has grown to over 422 lines and it now always jumps to > line > > 422 as the last line. The increment with the last jump threshold is 24 > > lines. Not sure what is magic about 24? My edit panel is sized to > display > > 20 lines. Resizing it to display more or less does not affect the last > line > > displayed. > > I looked for any suspicious hardcoded 24s or 23s but didn't see any. > > Hopefully Edward will have time to look at this soon. He's more > familiar with the relevant code than anyone else - I'd get to it > eventually, but yesterday's Leo file diffing tool was my Leo time for > this week. > > Cheers -Terry > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/l9PHhXhaO1IJ. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
jumpbug.leo
Description: Binary data
