By "large" I mean leaf nodes containing up to maybe 1200 lines of codes. About 6 such or smaller nodes in a file. It takes very noticeable amount of time to switch nodes. As I noted before qtGui alone contains over 10k lines and is only one part of the Leo file that contains many other source files, yet one is able to navigate around the nodes without effort.
On Saturday, September 29, 2012 12:16:33 AM UTC-7, F.S. wrote: > > > > On Friday, September 28, 2012 11:57:44 PM UTC-7, F.S. wrote: >> >> This was reported to the scroll issues thread already. I added a bit more >> details below: >> Rev 5465 is fairly unusable. >> 1) Switching between large nodes takes forever. It used to be snappy. >> > > Okay. I was wrong about the snappy part. The performance seems about the > same: switching between large nodes have been slow all along. I just didn't > notice it until I was testing the switching behavior because of the lost > cursor visibility, when how slow it is really stood out. How comes Leo is > able to open many large files quickly but can't handle a few large nodes? > > >> 2) Cursor is no longer visible if I navigate away from a node and then >> come back to it. Coming back to a node I always get the beginning lines. I >> believe the cursor position is not lost but is just out of view. It takes a >> lot of scrolling to get the cursor back in view again. >> >> On Friday, September 28, 2012 4:59:32 PM UTC-7, Edward K. Ream wrote: >>> >>> Please report any problems with the new code immediately. >>> >>> Edward >>> >>> -- 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/-/LEmF3ayB1zAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
