I'm not an expert on nav_qt.py. I'm not an expert on Leo-Editor. I'm working on a plugin to navigate the position visited list. Consequently, I've noticed a possible problem.
The position visited list grows without bound. This list is attribute "beadlist" of the instance of class NodeHistory. See leoCommands.py. Until recently, the position-visited-list was truncated by add-new- position-to-list (method update()) to the current position (i.e., beadPointer) whenever the "next" or "previous" buttons had been used to navigate to a previously visited position. This truncation was removed (using an "if 0") with the comment "This makes no sense." I agree that removing this truncation, makes the overall behavior of nav_qt.py much better. That is, more as one would expect. But it slightly worsens the unbounded list growth problem. Every outline position change goes into the position visited list and the list grows without bound. I have seen a position visited list with 158 entries. This might be considered a "memory leak." While this slow, small leak is unlikely ever to be a practical problem for anyone. A huge list is not very useful. I think making the list a 36-entry circular buffer (that overwrites the oldest entry) would be appropriate. I suggest 36 because this would make it the same size as the "Recent Files" list. The "Recent Files" menu has 36 entries because it uses 0 to 9 and A to Z as shortcuts. Note: Even when nav_qt.py is NOT enabled, the positions visit list grows without bound. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. 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.
