On Sat, Oct 18, 2008 at 9:44 AM, thyrsus <[EMAIL PROTECTED]> wrote: > > Itr's a only little more subtle: the first time a vnode of a > particular gnx is encountered, it gets put out in its entirety, just > as before - <vh></vh> and child vnodes. On subsequent occasions > (which happen because of clones) I put out > > "<v t="%s" %s></v>" % (gnx,attrs) > > which preserves open/close status and whatever other attributes the > vnode has -- but this does not put out the <vh></vh> or child vnodes, > because the current design of leo (at least since "graph" > implementation) reaches those attributes through a common tnode and > they are thus necessarily identical.
Sorry for the delay in responding. If you are confident about the code, I suggest merging it into the trunk. Please do a trial merge first: create a copy of your branch, merge the trunk into that copy, fix conflicts and run all unit tests. Repeat until no conflicts and all unit tests pass. I have found that when the trial merge goes smoothly the final merge of the result into the trunk is an anti-climax. Just make sure to report this major change in a separate thread here. So press on, and don't worry. The worst that could happen is that we would revert a branch in the trunk. Not a big deal, especially considering the low level of activity of the trunk just now, while Ville is on his honeymoon :-) Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
