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.
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.
Still Waiting 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.