Hi Edward
On Monday, 21 October 2013 17:55:09 UTC+1, Edward K. Ream wrote: > > On Mon, Oct 21, 2013 at 11:50 AM, Don Dwiggins > <[email protected]<javascript:> > > wrote: > >> On 10/18/13 7:42 AM, jkn wrote: >> >>> For clarity, I might point out this corresponding action from Ecco Pro >>> for getting items to the first child of a node >>> >> I'd like to second jkn's wish. > > > Yes, this will happen, but not for b1 ;-) > Thanks for planning to take a look at this ;-). As a result of this conversation I re-realised that Leo's (to me) non-inuitive behaviour on moving nodes is one thing that hinders my increased use of it as an outliner. I started to take a look at the underlying code a little myself; it'd be nice to have a first stab at an implementation for you to polish... As well as looking at the code I went to the recent Leo Cheat Sheet (great work, BTW). Can I just confirm that there are some minor errors in the documentation of the position class? You have two lists of methods: 'operations on nodes' and 'moving positions': i) I think the contents two lists are supposed to be mutually exclusive; is that right? ii) if so, then note that p.moveAfter(), p.movetoroot() and p.movetoNthChildOf() appear in both lists iii) I think the first list is missing (perhaps deliberately) p.insertAsFirstChild() and p.insertAsLastChild() Understanding whether I'm on the right track here would help my understanding, thaks ;-) Regards jon n -- 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.
