On Wednesday, December 10, 2014 3:44:49 PM UTC-6, Matt Wilkie wrote: > > > Sometimes this can be worked around a little more smoothly by creating a > temporary organizer node and putting all the children-to-remain-clones in > that before copy org-node and-paste-as-clone. So, 2 or 3 steps instead of > n*n steps. > > Thanks! This is pretty much what I ended up doing.
> I'm curious about what produces the want to copy-but-not-clone only the > parent in the first place. I don't think I've had encountered that yet. > What are you doing that makes this desirable? > > This would be helpful when one wants to have a templete node for multiple documents that share majority of contents. For example, let's say I'm making syllabuses for multiple sections of the same course. Then they will share majority of contents, but there will be differences such as class information, class meeting time and exam schedules, etc. With this particular functionality, I can make a templete, with nodes for both common and non-common contents, and then make the nodes for the common contents clones. For each class, I can just make a deep copy of the template, and edit non-common nodes. But it seems currently I cannot do this. So I ended up puttting the common contents into one parent node as you said, and manually generate other nodes. Which is not ideal because 1) you have to do quite a few reorganization of the nodes if you did not plan the structure beforehand, and 2) you still have to manually generate non-clone nodes. -Joon -- 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/d/optout.
