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.
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.
Tomas As commented
I would call this function DUPLICATE like in layers. Why create new components from scratch, when i could just duplicate one i need to change just a little bit.
For the love of all that is holy, please hear our screams.
Bartłomiej Płoszyński commented
Did you guys find any workaround for that?
Yes, please implement this, Adobe.
Recreating a component is so energy draining when you know a computer should be able to do it for you...
Zigmas Mallol commented
Totally needed guys... The states update was great, and helped a lot... but not being able to do this means we are having lots of trouble modifying those "Very similar" components with states.
Guys, for now, you maybe can do as I do when I've to do many similar components:
1) Take the master component and paste it into a new empty file.
2) On the Assets view, right-click the asset and make it a local component.
3) Paste it back into the original document, that way you can have a duplicate master component ready to be modified and with all the original states.
Also need this - massive pain in the ass having to duplicate effort when it could easily be solved by duplicating an exisiting master.
Josué Sotelo commented
I need this so bad. Would be a time saver
Matt DeMeis commented
Agree! And it's not just buttons. This is essentially keeping me from porting over a UI system from sketch to xd. I can't devote days of time to rebuild every state of every component. That would be bonkers The import works great if you have single state components, but who does that? Until you guys can be resolve that we'll have to stay in Sketch.
This would be soooo helpful. Copying and renaming a master component and then changing it or adding a state is essential. Otherwise you are duplicating work.
Another use case for this is creating a bunch of components which are very similar but just different enough to need to be separate, or when iterating a component. Maybe they have the same states but slightly different layouts. Maybe they have the same layout but you want to create a few different themes. Once you change the color of one of these instances, it may not reliably update without resetting to Master State once it has been altered. Obviously, if it's a whole new color scheme, maybe has some different text, etc, resetting to master state will be very tedious and frustrating.