On Wed, Jun 12, 2013 at 3:53 AM, Fidel Pérez <[email protected]> wrote:
> Anyway the more I think about it the more I dont realy understand how come > we canot refer nodes in a static way, so Im asking again in case it already > exists: > > Are vNodes static? > I'm not entirely sure what you mean by static, but I think the answer is yes. vnodes contain all of Leo's outline data. The data in a vnode represents all the data in a node. All clones of the same node are the same vnode. For any vnode v, v.h, v.b and v.gnx don't change, no matter how many times the node is cloned. (Cloning will probably change the contents of v.parents and v.parents fields.) I think vNodes should have associated reference number each, which would > stay the same until its deleted (even if we change the outline or > open/close the document). > That's the v.gnx property, which refers to the v.fileIndex ivar. This way we could easily refer vNodes from outside an outcome, and easier > from within the current outcome. The way would be: > New vNode -> New refference number, different to any existing one in that > outline > > Is there such a thing as a stable ID number per vNode? > Yes, v.fileIndex, aka v.gnx. Using v.gnx is preferable, because it is simpler. 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.
