> what is important is that when changing one clone, every other clone
> object will change accordingly. That's the important part of that wish...
Hi JTB - the part of your wish about making a clone by the copy command is available right now - that's what is mentioned in that other thread.
To make a clone that updates, use the Transform/Copy command, then select the new copied object, then run Edit/History and push the "Enable Update" button.
After doing that, you will have clone objects that will update when you edit the original.
This works because when you do the copy, the history of the copy command is stored on the copied object. But by default history updates are turned off for the results of copy - if you turn on updating for those objects then the history will kick in when you edit the original object.
You can do the same thing for several other commands as well - for example after you do a mirror, you can enable history updates on the new object, and it will then update when you edit the original.
But this does not work right now for Array though, there is a bit of a complication on certain operations that generate multiple outputs in one go, such as Array. Eventually this will get tuned up to work in a similar manner.
- Michael
|