On Mon, Sep 23, 2013 at 10:30 AM, Terry Brown <[email protected]>wrote:
> In particular, the call to p.moveToRoot handles a lot of details > > not likely to be handled by a virtual root position. > > There's the nub, can a specially constructed position work this way? > I'm not familiar enough with positions / vnodes to know. > Not without changing insertAsNthChild. That would open a can of worms, and possibly a Pandora's box. Let's be clear: the notion of a virtual root *position* is fraught with difficulties. Every commander has a hidden root *vnode*. Positions are not vnodes, and none of Leo's fundamental code in leoNodes.py was ever designed with a virtual root position in mind. The possibilities for subtle, data-losing, unwarranted assumptions is *way* too large to consider. Instead, Leo scripts must learn to deal with what exists. 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.
