Create new master 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.
Thomas Hale commented
This would save so much time in having to replicate states that are similar between components. For example, my design system has table cell components that have different height variants (as well as all the other "states" you might expect of such a component), thus if I want to create a component where all the states are virtually the same name and only difference is the height, I have to do a lot of work to replicate that structure of states, naming.
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.
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.
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.
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.
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.
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.
Bartłomiej Płoszyński commented
Did you guys find any workaround for that?
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.
Martin K. commented
It's helpful if you make a UI Kit with all button states shown for example. For now I have to set all states with every new button component I create (primary, default, flat etc.) by hand.
Oftentimes wile modifying a child component I reach a point where it needs to be a new Master component. Depending on the complexity of the component, recreating it as a Master can be taxing.
Right-click on a child component and change it to a new Master component.
Robert Erdt commented
Yes, it's such a pain with large grouped items to have to ungroup, re-group. Please up-vote this feature.
Especially when you have to design many states within states, developers want each component named accordingly, not states. Or you follow a specific design schema, and you have to duplicate each component to meet these requirements, this feature would double the time it takes.
Justin B. commented
It would be great to have the ability to quickly convert an -instance- of a component into its own -master- component.
Presently, when we copy or duplicate a master component it automatically just creates an instance. There should really be an easier way to convert any instance into a new master instead of having to select the elements of the instance, make it into a new group, and then make the group a new component.
This would save a lot of time if there was merely an option to right-click on an instance and select the "convert to master" option.