On Wednesday, August 7, 2013 4:52:45 PM UTC-5, Jacob Peck wrote: > The docs on c.vnode2allPositions() say that it doesn't really search for > *all* positions, just positions within v's distinct parents. Is there ever > a situation where this wouldn't grab *all* positions? I'm thinking if one > of the clones was a top-level node, there might be issues. Additionally, I > haven't looked into the code dealing with chapters - are there special > cases for clones in other chapters? >
The only way to know is to look at the code... At first glace, all seems well. What I looked for is something *other* than fundamental vnode operations. There are none. Chapters are implemented much as hoists are implemented. And the hoistStack is somewhat of a hack. It "infects" quite a few commands, as well as the drawing code. Happily, the hoistStack *never* is involved in the fundamental vnode data structures. Thus, neither hoists nor chapters will have any effect on the underlying vnodes. Leo would be severely broken otherwise. Yours is a very perceptive question. It shows you are paying attention to subtle implementation issues. 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
