Create new main component from existing component
After releasing "State" feature, it's been able to prepare complex interactions like "hover." Following feature may help to reduce required time preparing a new component with similar behaviors/instructions.
New component with state settings every time when a similar behavior is expected in different look and feel.
(Currently, preparing another XD file is believed to be the only solution to avoid this by selecting "Make it as local component" after loading it from another XD file.")
By select "Use it as a new Master Component" is to make a new Master component instead of copying it as an instance component.
◆ Why is this valuable to you?
When using a single, new XD file and load a master component from other XD files, it is possible to make it "local component"; however, it is unable to make it happen within the same XD file.
This helps to reduce time to prepare a set of basic state setting from the beginning each time. This also helps NOT to get affected unconsciously on the new component by editing the template master component by someone else.
Since Co-Editing feature is now beta version, some larger project may have a couple of co-editors of components on the same XD file in the future. While a group of designers keeps upgrading a basic behaviors for future use, another group of designers is working on on-going project to finalize a specific look and feel based on the template component.
Joo Chung commented
Adobe appears to care very little about things that actually improve the user experience of this software. So many basic, basic features are lacking, such as this one. Other functions overtly obliterate user work, which leads to having to do workarounds for functionality that really should be as basic as being able to copy and paste. Get your shit together Adobe.
C. Lockeby commented
Here's another +1 for this idea. Ungrouping and rebuilding all states isn't an efficient workflow!
Evangelion Netai commented
yes pleaseeee need
It would be a huge improvement to create new master components from the overrides of a component.
currently, i have to ungroup the component and create a new one, if i want to create a new master component from override styles.
but therefore, i have to recreate states etc., which could be easily adjusted otherwise.
James Duffield commented
Having to recreate all states on a new component is a real pain. This is 100% needed.
Mirek Ždímal commented
+ 1 for a master component duplication method
Josh On commented
Just ran into this again.
It is really important - the use case I have is that I have an alternative navigation on some screens and now I have to rebuild the whole nav component...
Amanda Staunton commented
Please work on this Adobe, this would be a major time saver. It's frustrating to have to remake a component that has multiple states.
Tony Ward Arts commented
Absolutely my #1 need right now! Please make it happen... Working on my own website design and this is crucial.
A workaround for those looking for one like me: Copy then "Ungroup Component" then "Group" the same elements (they will stay selected) and "Make Component" that new group.
Max Zin commented
Yes please much needed!!!!
Jake Spillar commented
Thoughts and prayers this becomes a thing.
Desislava Slavkova commented
Please add this! It's such a hassle to have to redo from scratch very similar components and it sounds like such a simple feature. It would speed by a lot my design process.
That' s important for faster working. Often I change a master component in my design. When it's good I'd like to transfer/apply it to every of the components on my project
At the moment I have to copy and paste and make it like i changed.
Nik Yabo commented
All buttons or components must have easier navigation.. with this feature we can easily copy and paste let's say a button and turn it in to a different master component. this would ease workflow alot.
Justin Arendt commented
Dido, this would be great! Creating a form library and for every form element have to recreate focus/disabled states a lot of extra tedious work involved. In addition, would be nice to be able to sort the states so you can edit rearrange and to make them consistent.
I have found a workaround for this problem. Copy the component you'd like to create a new version of into a new document. In the assets panel right click and select "make local component". You can now copy and paste it back to the original document.
Nathan Wells commented
I'm echoing what everyone here is saying. It's a massive waste of time to manually recreate components that should be a simple copy/paste operation.