On Friday, May 22, 2020 at 11:08:19 AM UTC-4, Edward K. Ream wrote:
> On Wed, May 20, 2020 at 9:06 AM Thomas Passin <[email protected] > <javascript:>> wrote: > >> What should happen when I copy a tree that contains a clone? >> > > Leo copies the tree to the clipboard as is, that is, *retaining *gnx's. > What happens next depends on how you *paste* the tree: > > - The paste-node (Ctrl-Shift-v), command allocates *new* gnx's for all > pasted nodes. > - The paste-retaining-clones command (Paste Node As Clone, from the > Outline menu), retains the gnx's for all pasted nodes. > > Either way, if the pasted tree contains clones (nodes with more than one > link to them in the pasted tree) then those nodes will be cloned after the > paste. > This sounds as if a cloned node in the original tree will end up as a cloned node in the final tree. That is not what I see, though. The node that is a clone in the original tree becomes a copy (not a clone) in the pasted tree. That would fit in with "new gnx's for all pasted nodes". I don't want to clone the entire tree, because the whole point is to modify the original while keeping most of it as is. For example, I might add some imports, or make some new constant assignments. I don't want to end up with two import nodes (one the cloned one and one for new imports) or two Declaration nodes just so I can add lines to the skeleton of the original. It's not a big issue for me but I expected that a cloned node in the original would end up still being a clone in the copy. If that was the intent, then there is a bug. If it was not the intent, well, OK. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/4fcf901b-5f0e-4098-9add-91f32d237f4e%40googlegroups.com.
