I had a suspicion that a plugin could be causing the problem. Sure enough the 
todo.py plugin causes the significant lack of visual updates. Even with all 
plugins disable traversing the list using Up/Down-arrow is still a little 
choppy but much much better. It is only the todo.py plugin which causes the 
significant lag in visual updating in the tree, however.

That said, there is still visual lag when holding down Ctrl+Up or Ctrl+Down 
in the body which moves a line of text. That may be a whole other 
bug/issue. Can somebody confirm if they're seeing this behavior?


On Friday, May 29, 2015 at 6:22:30 AM UTC-4, john lunzer wrote:
>
> It may not be enough to say that Leo has no control over it. As you say 
> this is probably mostly able PyQt and there may be a workaround to whatever 
> is going on. Additionally if I create my own PyQt app and add a QTreeView I 
> can easily traverse up and down the list without issue, here is an example 
> <https://wiki.python.org/moin/PyQt/Creating%20a%20context%20menu%20for%20a%20tree%20view>
>  
> that will create a stand alone tree view.
>
> Anyways since I'm not sure I gave my full setup here is what Leo reports:
>
> Leo 5.1-final, build 20150430065234, Thu Apr 30 06:52:34 CDT 2015
> Git repo info: branch = master, commit = 6325d1c54d1b
> Python 2.7.8, PyQt version 4.8.6
> Windows 7 AMD64 (build 6.1.7601) SP1
>
> On Thursday, May 28, 2015 at 4:41:02 PM UTC-4, Chris George wrote:
>>
>> There are many versions of Windows, and many different possible 
>> combinations of Qt, Python, etc. etc.
>>
>>
>> Leo has no control over any of that. 
>>
>> Funny how business always feels that tighter control on process leads to 
>> better results.
>>
>> Chris
>>
>> On Thu, May 28, 2015 at 1:18 PM, john lunzer <[email protected]> wrote:
>>
>>> Would if I could! At work they make me use Windows, otherwise I would 
>>> definitely be using Linux.
>>>
>>> Also as Edward pointed out he uses Windows and is not experiencing the 
>>> problem, which is extra confusing for me.
>>>
>>> On Thursday, May 28, 2015 at 4:14:14 PM UTC-4, Chris George wrote:
>>>>
>>>> Why not just switch operating systems instead of making accommodations? 
>>>>
>>>> :-)
>>>>
>>>> Chris
>>>>
>>>> On Thu, May 28, 2015 at 12:35 PM, 'Terry Brown' via leo-editor <
>>>> [email protected]> wrote:
>>>>
>>>>> On Thu, 28 May 2015 12:26:05 -0700 (PDT)
>>>>> john lunzer <[email protected]> wrote:
>>>>>
>>>>> > Not as if anyone is actually interested but I implemented
>>>>> > goto-next-N-visible in a much faster way:
>>>>>
>>>>> You want this because holding up/down-arrow to move through the outline
>>>>> is too slow?  I've noticed that too.
>>>>>
>>>>> Would you want 'else: break' in the if, just to save those valuable
>>>>> microseconds?
>>>>>
>>>>> Cheers -Terry
>>>>>
>>>>> > @language python
>>>>> >
>>>>> > N=5
>>>>> >
>>>>> > def getVisNextN(n):
>>>>> >
>>>>> >     current = c.p
>>>>> >
>>>>> >     for ind in range(n):
>>>>> >
>>>>> >         forward = current.getVisNext(c)
>>>>> >
>>>>> >         if forward != None:
>>>>> >
>>>>> >             current = forward
>>>>> >
>>>>> >     return current
>>>>> >
>>>>> >
>>>>> >
>>>>> > NAhead = getVisNextN(N)
>>>>> >
>>>>> > c.setCurrentPosition(NAhead)
>>>>> >
>>>>> > c.redraw()
>>>>> >
>>>>> > I find this extremely useful (when bound to a key shortcut) for
>>>>> > quickly navigating an outline when lots of nodes are expanded. Can be
>>>>> > easily modified for goto-prev-N-visible.
>>>>> >
>>>>> > On Thursday, May 21, 2015 at 6:22:35 AM UTC-4, Edward K. Ream wrote:
>>>>> > >
>>>>> > > On Wed, May 20, 2015 at 11:40 AM, john lunzer <[email protected]
>>>>> > > <javascript:>> wrote:
>>>>> > >
>>>>> > >> Thanks for the report. Edward what is your setup? Are you on
>>>>> > >> windows or linux?
>>>>> > >>
>>>>> > >
>>>>> > > Both.  I do most of my work on Windows because the fonts are
>>>>> > > clearer and sharper on that machine.  Soon after a commit I'll
>>>>> > > rerun all unit tests on the Linux machine.
>>>>> > >
>>>>> > > Edward
>>>>> > >
>>>>> >
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "leo-editor" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> Visit this group at http://groups.google.com/group/leo-editor.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "leo-editor" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/leo-editor.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to