THIS for all the reasons mentioned but also to be able to recover from breaking bugs. I reported a big that I can not predictably recreate. It involved heavily nested master components and changing the nested components and other layers in some instances. The bug would brick a file and make 'copy' and 'paste' not work for the offending components as well as 'undo' not working across the entire file. Because my master components are heavily nested, I can simply start a new file with instances and then unlink and re-componentize the top parent component as all the nested components also become unlinked.
Being able to 'make master' would be ideal. The UI could work like a 'find and replace' and suggest how many instances are in the document, how many are in other documents, etc. and at least offer me the opportunity to retarget the ones in the same document to the new master, if not all instances across many documents.
casey
supported this idea
·
THIS for all the reasons mentioned but also to be able to recover from breaking bugs. I reported a big that I can not predictably recreate. It involved heavily nested master components and changing the nested components and other layers in some instances. The bug would brick a file and make 'copy' and 'paste' not work for the offending components as well as 'undo' not working across the entire file. Because my master components are heavily nested, I can simply start a new file with instances and then unlink and re-componentize the top parent component as all the nested components also become unlinked.
Being able to 'make master' would be ideal. The UI could work like a 'find and replace' and suggest how many instances are in the document, how many are in other documents, etc. and at least offer me the opportunity to retarget the ones in the same document to the new master, if not all instances across many documents.