On Sat, Jul 4, 2009 at 10:13 PM, Edward K. Ream<[email protected]> wrote:
> BTW, this would also be the end of tnodes, and all the confusion > regarding vnodes vs tnodes, t.uA's vs. v.uA's, etc. etc. Relevant, because I was just now hit with this (for my next cool tweak regarding contextmenu, "collect under" that uses multiselection): It will also allow node api users to operate on nodes directly in "documented" fashion, instead of having to go through positions. Positions are bad sometimes, because their meaning changes when the tree changes. If you want to move 30 nodes under node n, you can just do p.moveToLastChildOf(n) in a loop. With positions, this doesn't work (well, it works, but gives lots of assert failures and undo doesn't work). positions are relevant as tree iterators (in the meaning of "positions on screen"), but are no longer a necessary middleman for all tree operations for "bookkeeping". -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
