Thanks for those details and info! Wanting to refresh the least possible parts of the UI at each user action is what caused me to return into sheding some light on those details... Exploring further, and trying out more available options in vscode's refresh and rendering has made this issue less problematic.
Expect a merge into dev, ...and maybe even into master soon :) -- Félix On Thursday, August 13, 2020 at 2:08:12 PM UTC-4, Edward K. Ream wrote: > > On Thu, Aug 13, 2020 at 12:26 PM Félix <[email protected] <javascript:>> > wrote: > >> More Details: I'm currently testing keeping the (id) identity of nodes >> with a *murmurhash* of their 'archived positions' json string >> representation. Also, in vscode, the collapsed state is preserved by the >> said 'id'... Thats why i'm looking into clone expand/collapse *exact* >> behavior matching. >> > > Besides the settings I just mentioned, there is some clever code/hack > relating to associating positions with vnodes. I don't remember who did > what, but I think both Vitalije and I had a hand in the code. > > I see that v.__init__ has an expandedPositions ivar. A cff on that should > tell you what is going on. I just took a look. I didn't remember any of > this, but it seems fairly straightforward. Some parts do explicitly involve > clones. > > Edward > -- 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/7402a9bf-6890-4401-9c70-5809cf66fd94o%40googlegroups.com.
