On Fri, 5 Jun 2015 04:34:07 -0700 (PDT) john lunzer <[email protected]> wrote:
> > I've experienced the same annoying slow, non-updating tree movement > > with the up/down key navigation. I didn't think to look into the > > plugins. Lo and behold, removing the todo plugin fixes that > > problem for me too! There is only a barely noticeable visual lag > > remaining now (which may well be due to syntax highlighting, but I > > thought highlighting was delayed so that it didn't interfere). > > Thanks for the tip! > > Good to get this verified! > > I didn't know this shortcut existed; it will probably get used a lot > from > > now on. I can confirm that this slow visual updating behaviour > > remains for me, even after removing the todo plugin. > > Also good to get this verified. From my tests for this one it didn't > make a difference if it the todo plugin was enabled. However it does Well, I'm definitely seeing Todo.py related slow down, and will attempt to investigate that. Cheers -Terry > make a difference if the node is syntax highlighted. Even @language > rest creates this slowdown. With no syntax highlight what-so-ever > then the visual updating is smooth sailing. > > I think both of these could be considered a bug related to syntax > highlighting (ie these are not desired behaviors), I think my > previous suggestion of not performing syntax highlighting if holding > down Up/Down in the tree or not updating syntax highlighting if > holding down Ctrl+Up/Down in the body and waiting for a key release > event might solve both of these issues. If we can't find a quick > solution and it's because the speed of syntax highlighting is > negatively impacting other parts of Leo then I think the speed of > syntax highlighting needs to at least be considered an "issue" that > should to be on Leo's roadmap. > > I would like to get peoples' thoughts. > > On Thursday, June 4, 2015 at 9:29:16 PM UTC-4, Peter Mills wrote: > > > > On Friday, May 29, 2015 at 9:02:32 PM UTC+10, john lunzer wrote: > >> > >> 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. > > > > I've experienced the same annoying slow, non-updating tree movement > > with the up/down key navigation. I didn't think to look into the > > plugins. Lo and behold, removing the todo plugin fixes that > > problem for me too! There is only a barely noticeable visual lag > > remaining now (which may well be due to syntax highlighting, but I > > thought highlighting was delayed so that it didn't interfere). > > Thanks for the tip! > > > > Leo 5.1-final, build 20150421110203, Tue Apr 21 11:02:03 CDT 2015 > > Python 2.7.6, PyQt version 4.8.4 > > Windows 8 AMD64 (build 6.2.9200) > > > > 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? > > > > I didn't know this shortcut existed; it will probably get used a > > lot from now on. I can confirm that this slow visual updating > > behaviour remains for me, even after removing the todo plugin. > > On Thursday, June 4, 2015 at 9:29:16 PM UTC-4, Peter Mills wrote: > > > > On Friday, May 29, 2015 at 9:02:32 PM UTC+10, john lunzer wrote: > >> > >> 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. > > > > I've experienced the same annoying slow, non-updating tree movement > > with the up/down key navigation. I didn't think to look into the > > plugins. Lo and behold, removing the todo plugin fixes that > > problem for me too! There is only a barely noticeable visual lag > > remaining now (which may well be due to syntax highlighting, but I > > thought highlighting was delayed so that it didn't interfere). > > Thanks for the tip! > > > > Leo 5.1-final, build 20150421110203, Tue Apr 21 11:02:03 CDT 2015 > > Python 2.7.6, PyQt version 4.8.4 > > Windows 8 AMD64 (build 6.2.9200) > > > > 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? > > > > I didn't know this shortcut existed; it will probably get used a > > lot from now on. I can confirm that this slow visual updating > > behaviour remains for me, even after removing the todo plugin. -- 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.
