On Thursday, August 13, 2020 at 7:21:38 PM UTC+2, Félix wrote: > > To Edward, or Vitalije, ... or anyone really :) > > (trying to debug yet another behavior in leoInteg, only to find out that > Leo does it in the first place, so my code was correct all along!!) > > I am sorry for being late, but the behavior that you see is just a consequence of the position instability. When you insert a node in to the tree (or delete one), positions of all following siblings and their subtrees become invalid. Leo decides which nodes should be expanded by keeping track of the expanded positions. When those positions become invalid the information is lost. There is nothing you can do about it at the moment.
I've made some experiments with outline drawing code that use native qt tree item indexes instead of positions but that has not been merged into the devel branch. To be able to use qt tree item indexes instead of positions, Leo have to keep track of all drawn tree items and not to discard them on each redraw, but that is not how Leo draws tree at the moment. Lately I am too busy working on some other stuff, so I can't work on Leo. Once I get more time, I plan to continue my work on the issue 1598, which might lead to some improvements in the way Leo handles positions/vnodes and drawing. Vitalije -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/fa09c653-0b92-490f-9038-2ff61d4f8c0ao%40googlegroups.com.
