Create new main component from existing component
◆ Overview
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.
◆ Actual
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.")
◆ Expected
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.
Kei ™
shared this idea
-
misagh mohamadzadeh commented
I totally need this. This is crazy what XD can't do. SO annoying!
-
Erin-Anne
commented
I would like to be able to right click on an existing master component and duplicate it. It would then become it's own master, and I could make changes to it without having to create all the states again.
A simple example is if you are creating different brand language concepts and you create a master component like a button or a dropdown menu. You created your first one and added all the states to use throughout your first concept. Then you want to make a second VBL concept, but you want to create a new master component to use throughout the second concept. Right now I could do that with either overrides, or from scratch, but then I have to add all the states in again. This is frustrating when you want to create common components for multiple concepts.
-
Mo Baba commented
I have found a work around to this situation and it works quite well!
After making the instance local (which still relies on going to the original Master and therefore doesn't solve the problem we are facing), I used CMD+Shift+K and the instance became a master. I am now able to use it as I want!
But this process can only be executed in a new file. If done in the same file as the original Master, CMD+Shift+K will go to that original Master instead of creating a new, independent Master.
I made screenshots in the attached.
Please let me know if this works for you too.
-
Tekin commented
I think the workaround could be moving a component to another file make it local, do all the changes and copy it back to original file and make it local there. I will try that but this should have been the earliest features in XD.
-
Tadiane Oliveira commented
We urgently need the functionality to create master component from instance.
-
Tadiane Oliveira commented
At least some plugin has appeared that makes it possible to create a new master component from a changed component?
-
The 'Use it as a new master component' will actually be very helpful. I have edited master components affecting their instances when that was not the purpose. I want to be able to turn some instances into masters so that edits on the 1st master will not affect the instances.
-
Anonymous
commented
Really need this feature, would save so much time undoing and redoing work.
-
Anonymous
commented
Please add this feature ASAP. It's crazy to require users to duplicate work on very complex components when they need similar behavior with subtle differences. Please help!
-
Delve Formative
commented
Please, please, please add this.
-
Sam Chan commented
I'm sure the release of this feature is just a part of some huge unveil that'll change our worlds :)
-
Matt
commented
Are the Product people at Adobe listening?
-
CypherPoet
commented
👍
AdobeXD is awesome. This feature would make it more awesome.
-
Celestine Fisser
commented
Adobe should pay me for every wasted click to rebuild components over and over again
-
Sue I
commented
Why do you continue to make the design process longer and more difficult for your users?
If I could bin using XD I would. It is so far behind Figma and Sketch, it's past a joke.
-
Han-Chia Chen commented
I do not understand how this is not a feature yet.
-
Nik Yabo commented
When making buttons it's really annoying that I have to create components for each of the buttons. And especially if it has hover states, I am forced to ungroup component and group it again just so it becomes the "master component"
Hope there's a feature to make instance a "master component" of its own while keeping all the attributes added (hover state and etc).
I'm sure that's not so hard to do right?
-
Anonymous
commented
The copy/paste into another doc > make local hack mentioned below doesn't work anymore since linked components have been deprecated in favor of shared libraries. 😢 No reason I can think of why this isn't possible yet. I've lost hours and hours of work as a result of this not being possible.
-
Peter
commented
Yes please, we need this feature.
-
Andy Grooms
commented
I've just run into this problem - the lack of the feature described is exactly what is holding me up. Thanks to those who have provided the workaround. This feature would really help speed up my workflow.
