Add Component copy behaviour
See original GitHub issueImplement explicit copy behaviour
>>> c1 = Cube(size=10)
>>> c2 = c1.copy()
>>> from copy import copy
>>> c3 = copy(c1)
Both methods create objects independent of the original; changes to c1
do not effect its copies.
Assembly
component copies would be nested.
Question
Is there a way to intelligently copy a Component
before its been built, so that the original, and the copy are only built once…
Initial implementation, probably avoid the tricks; keep it simple stupid (KISS principal)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Fusion 360 - Copied Component Behaviour - YouTube
A short video showing how copied components behave and how to manage them.If you have found this video useful and would like to...
Read more >copy components in hierarcy - editor script - Unity Forum
This script copies colliders, rigidbodies, scripts, animations, and character joints from an object hierarcy to an other hierarchy.
Read more >Customizing Copy Behavior - Visual Studio - Microsoft Learn
Customizing Copy Behavior · Applies to: · Enable or disable copy, cut, and paste. · Copy links to the same target. · Rapidly...
Read more >What is the correct way to copy a component? - Stack Overflow
Considering that variable-to-variable copy is a beginner way, I am looking for a solution that can copy any component using the Generic method....
Read more >Create a `copy` `paste` behaviour component · Issue #12 · zambezi ...
Some components, like the WIP grid highlight component need to understand copy + paste; a bespoke solution is being "organically" grown on the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gntech yep!, that’s a good argument! I love it 😉
And my opinion is that there should be no different behaviour for Parts vs Assembly.