Really essential functionality for the usability of this tool. Major nuisance in the core workflow!

Honestly quite disappointing that this isn't working.

This is a must have ......

Keep thinking that Figma is Way ahead of Adobe for things like this... I'm kind of regretting on keep growing my learning curve in Adobe XD and thinking seriously on just going to Figma.

Yes, Please!! Fix this Adobe. I believe Figma is doing it the right way already. : (

Please make this happen! Updating component states is the biggest waste of my time in XD. :((((

Please!!!

Please, please, please. I am begging.

Still under review ???

My team currently spends a lot of time updating elements across our component states when we want to show state transitions in our prototypes. Allowing your users to set component constituents as static / inherit would save a lot of time. Since we are constantly updating states and component variations it would also help to be able to shift the order of our component states.

Would also be handy if we could freely move the states in any order we want. I'm hoping Adobe team already knows about this and will hopefully give it to us in the next release. Let's keep our spirits up! Adobe is always doing a great job thanks to their talented team.

Inheritance can come really handy. It will speed up my process nearly 4 times.

Sometimes a component containing various states is pre-made.

However, when the size needs to be changed, only the current state will change, and other states will not change at all.

The application of component functions is restricted.

After all, in the drawing board, it is unlikely that the same component requires only one size.

Some components may be too complex to just include scaling functionality by default across all states but I agree that having a checkbox to toggle "scale all component states" would be extremely handy with simpler components like custom icons, buttons, and input fields (this last item especially).

Please fix this one... and while at it... add override master symbol too...

Please, fix this! It's really needed!

One ugly work-around to this is to use a sub-component that holds all of the state modifications. So if you have a Button master component, add the template text, then nest a Button_State component instance inside it that holds everything else (background, shadow, etc.). The Button component doesn't have any states, but the Button_State component does.

Then for every Button component instance, you can modify the text at will, then click through into the nested Button_State component and change the state. One limitation to this workaround is that you can't modify the text properties (colour, size, etc.) because it's not located inside Button_State. Also, you'll have twice as many components so best to use a consistent naming scheme.

Any updates on this?

Should be available in the next release! (Xd 37.x.x 🤞)

There are moments where you'd want the instance to have different states that aren't copied. For example if you are trying to do a specific override.

I think this requires a little thought, which is why it's still under review. Maybe if "default" were template instead and you are required to create all states from there.

I already do that in some cases already where I'll leave the default as the true master then create a new default state so if I have to go back and make a change to only the default, it doesn't make that change on all of my other states that I then have to go through and make changes to all the other states to undo it.

That being said. I'd love to be able to make text and size changes on a copied component in that "Default/Template" state and make it transfer to the other states in this instance.

totally agree with it!