On Tue, 22 Apr 2008 14:40:57 -0500 "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> > Given that you can arrive at the same node by different paths, I > > think a fully populated stack gives plugins a valuable tool for > > determining context, so I don't think it's just an internal > > implementation detail. > > Hmm. p.parent, p.directParents, p.parents_iter, > p.self_and_parents_iter and p.isAncestorOf are the recommended way of > determining context. They should usually suffice. Plugins that want > to remember positions in uA's must use p.archivedPosition. So I > still think that the stack is better thought of as a black box. True, true of course as p.parents_iter gives you the path and works out what's happening with clones, doing any required vnode funkiness. In unified node world it seems p.parents_iter would just iterate p.stack. Unless it was being used to generate p.stack, but that seems unlikely? I really should stop conjecturing and look at the code :-} Cheers -Terry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
