@pascal @wim
Can you address this to the right developers?
Problem:
The current attitude of copying every single material in the file + plugin data like visual arq together with something as simple as one single curve is MADNESS. It really bloats all other files, hogs system resources etc.
We have to be able to copy paste stuff. And we have to be able to keep files small and clean and not force a file to store plugindata that it should not have.
Workaround:
Using Export selected with save small to a file does not store all materials in the file and we can safely import it into another file. BUT do you think we do that??? That is like using a faxmachine when everybody else is using (ā¦no not email) SnapChat (itās 2020 after all)
Situation:
As I have understood it Ctrl-C in a way saves to memory a rhino file containing the selected data, thus bringing materials that have nothing to do with the selected objects with it.
Proposal:
Can Ctrl-C be upgraded to use the export engine with save small instead? I canāt imagine that should be too difficult since you already have the code for that⦠(crossing fingers)
Footnote:
The last thing we all want is irrelevant stuff added to any plan or file, and the way it is now makes that happen every single day. And we have to clean up materials and other stuff.
In V7 I often see that a āmissing fontā warning pops up if I paste a curve from V6, and that is just nonsense. A curve does not have a font assigned. So this needs to be solved for V7 as well.
Please, I hope you understand the importance of this and that you see that allocating some resources for this both for v6 and v7 is time well spent.
@gustojunk Can you chime in on this if you have any thing to add?
You are much better than me in explaining stuff like this.