On Sunday, May 3, 2020 at 4:59:30 AM UTC+2, Félix wrote: > > I thought I was going crazy while trying to debug something weird in > leoInteg.... so I tested what I was doing directly in Leo and it turns out > it was Leo who was contracting nodes in the outline when I was selecting > nodes near the top and using the usual ctrl+i command to insert a node. > > This is known Leo's limitation. The expanded node state is using positions to allow expanded state per each separate clone. But positions become invalid when you insert node before them. It means that expanded state becomes invalidated too, therefore most of the states can't survive node insertion (or deletion) near the top.But this affects only clones and their subtrees.
HTH 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/3f0dd031-27ea-4cc7-8082-97f827868b63%40googlegroups.com.
