Copy a component inside the master component and edit the copy afterwards - does not reflect on rest!
A master component can consist of many other master components. Lets call them 'inside master components.
If one of these inside master components is duplicated in the master and then edited (fx. a text) the duplication is done correctly, but the edit does not work. Even if you rename the new inside master component.
After duplicate, I have to ungroup the duplicated one and make a new inside component before it works.
Please do something about this. Extremely annoying.
This is now available for you in today’s release of XD 34. Enjoy!
-
Henrik commented
There is still no opportunity to create a new component, if this object is a sub-component already.
I want to build an overall menu structure with different content depending on the role signed in.
The menu structure should be the same for every role and can be the master component.
Then I need further components for every role with the same structure as the master component an role-specific content and links. Lets call it sub-master-component.
At the moment I'm working with master components for every role. If I need to change any content or link, I can do it in the master component for that role. If I want to change the overall layout of the menu structure, I have to do it for every role-specific master component.
If there would be a possibility to create components inside components (should be the same object and not a smaller part of the master component), I can work with sub-master-components.
That would be helpful and I think that is the point in this request. Please open it again. -
Aleksandar commented
This is not done. It is the same behaviour in the update. We still don't have Inside Master Components. Take this scenario. I have main card component that can have 5 states. Now I want to make 2 rows that is going to contain the master components. If for example I want to change some text in the main card component (time for example) in just the second row I can not do that simply because you only have one master component. This should be done in a way that you can specify an instance component to became a master component for certain parent.
If you try to do a real design work then you are going to realise how buggy and untested your software is for more complicated scenarios.
I hope that you are going to do something about it for real and not saying that you have done it when you did not. Because of this kind of behaviour our company is thinking of switching to another software.