Participant

Answered

Feature Request-States do not inherit component instance default state modifications

Forum|Forum|6 years ago
November 7, 2019
44 replies
28568 views

Hi, so the scenario is as follows:

You make a button template component, that has a body shape with fill and border, and a text label.
For that component you add a state - let's say Hover, but any state works the same
You make an instance of the component. You adjust the button width and change the button's label (standard component usecase I suppose?)
You test the hover effect: of course the interaction is applied, but the instance adjustments were not inherited in any way for the instance's states - on hover the button's label changes back to the default placeholder, and the button auto-animates to the master's size.

I suppose the solution is to apply instance modifications to each of the instance's states separately, but that seems like something the component feature should address rather than require the user to do manually for every element.

The new states feature has been especially disappointing with an ongoing app design, where I already have most of the design system established. It was initially logical to me that I could add a Hover state to the component's master and all the instances, across the artboards in the entire prototype would "simply" inherit it, but alas - I found they only show the master's state on hover. Needed to undo all of that since it basically broke the prototype for any kind of use, and I definietely do not have the time to go instance-by-instance and apply all the component edits again.

Unless I missed something and am doing this wrong.

Missing feature

This topic has been closed for replies.

Correct answer Sherif Assaf

Hi All -

Apologies for the inconvenience around the effort required to manually change states in component instances.

We're actively working on addressing this issue so that changes made to the Default State in an instance would propagate to other states within that instance.

Stay Tuned.

Thanks,

Sherif

Show previous replies

J

jl36807489

Participating Frequently

I really hoped this was solved in v34 but it appears it is not unless I am doing something wrong

M

mschatzler

Participant

No it's not ...

But we have a cool 3D feature. Haha.

It's a total loss of time especially that the background shape inherits from its state on the main state, so why the text not ?

J

julia0D45

Participant

Wow! 1 year people are waiting for this obvious bug to be fixed...All prototyping tools have this option by default nowdays. Just recently moved from UXpin to Adobe XD and this issue is the one that causes biggest frustration.

K

Kristijan5CBE

Participant

This is a workaround, and was pointed out to me by a coworker who deserves all credit - Jatin Gupta. You are my hero.

In order to make the states inherit the original components states, the background of the button should be a component itself, with default, hover and pressed states.

Once it has been made a component, a mask (yes, a freaking mask) should be applied on top of the background of the button only.

Then the button label and button background should be grouped into one object with Padding checked.

Finally, that group should be made a component. and voila, use as you wish.

There is one caveat tho, the mask of the original component needs to be long enough to cover for all duplicates length.
As long as duplicate buttons are shorter in length, then the inherit instance will work without issues.

Hope this helps. Cheers.

D

davidd72619639

Participating Frequently

Still waiting ! 😊

T

Timothy5DEE

Participating Frequently

Thoughts and prayers - Adobe

H

hulmerous

Known Participant

Lol. Best response yet.

J

jonoyoung

Participant

Encountered a similar problem today, posted about it here:
Prevent Component Resize/Reset on State Change

A

Anonymous

Adobe, please fix this before anything else, it's too basic.

If you don't understand why - then we have a bigger problem here.

MatiouLilou

Known Participant

Hello,

I have to take the decision whether or not I delete all the states I've created for all my components because the interaction is a mess with this problem. But I don't want to delete them if you are going to tell me that this is going to be fixed in the next update. Can you be clear about this, please?

Spas K.

Community Expert

I'd say it's highly unlikely it will get fixed in the next update. Other features have been "Under Review" for years. You won't get a clear answer anyways.

I stopped using hover states for most things, or only use them one the main page.

Maiane Gabriele

Inspiring

This is so sad. 😕😕 I've been waiting for this feature for a long time. It's a terrible experience.

Instead of adding new features, they should focus on fix this kind of stuff. This is more important than new cool states interactions ou anything similar.

M

martinklausen1

Participant

Hoping Adobe is putting all their efforts into fixing components.. its too unreliable now. Nested components are very buggy..

HARSHIKA_VERMA

Community Manager

Hi All,

We understand your frustration and our team is actively working on this feature. I would request you to please submit your feedback here: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38973007-allow-component-instance-overrides-to-be-inherited and upvote the request to add your voice.

Hope it helps.

Thanks,

Harshika

R

RadAwayy

Participant

This means I just simply can't have a functional and interactive design system. So now I have to delete all my components states because when I interact with them it is absolutely ugly. This should not be a feature but a bug fix. What it the point of having a library of components with different states if you can't interact with them? It prevents me to do a good job in my company. This issue has been highlighted for a long time now and you can't even give us a proper time frame to fix the issue.

G

ginalintw

Participant

I ran into a similar issue today where I want to have an image zoom hover state (issue link: https://xd.adobe.com/view/feeeafea-fcdf-47b2-6427-a61245799ec1-88df/). When the default state is changed, I still need to change the hover state. Please fix this issue.

Thanks.

S

shachars4609109

Participant

This is simply a disgrace. I'd understand it if it affected more complicated components (still as a bug). But a BUTTON??

That's the most basic component you should have tested thouroughly but obviously didn't. A BUTTON! You CAN'T CREATE A PROPER COMPONENT FOR A **BUTTON**. If this is a sign of what's to come from Adobe, then I'm seriously considering finding alternatives for my team. If you guys at Adobe read this and don't see how absurd your replies on this thread are then there is no fix for you. FORGET silly features like the ability to play an audio file or voice commands. MAKE SURE THE BASICS WORK PROPERLY first. Sheesh.

S

stephenb84740223

Participant

Please, please fix this. This issue has crippled my workflow.

B

brycef46143366

Known Participant

Should never have released components like this in the first place. Haven't fixed yet? Inexcusable.

S

Sherif AssafCorrect answer

Adobe Employee

Hi All -

Apologies for the inconvenience around the effort required to manually change states in component instances.

We're actively working on addressing this issue so that changes made to the Default State in an instance would propagate to other states within that instance.

Stay Tuned.

Thanks,

Sherif

andre_fauri

Participating Frequently

I've encountered this issue today about states inheriting text labels even when it has been changed in instances and would like to share the images.
I was using a component for the day of the month in a calendar so I would be able to add states and test them in prototype with Current Day, Picked, etc..
It happens that when I try to change the state in a different day it brings the original text label of the component (1).

I think that if I could set what things I would like to inherit from the states (eg. text label content) this problem would be solved.

The images clarify a little bit more.

B

brycef46143366

Known Participant

Yep, this is exactly the same problem we've all been discussing. Clearly a bug in Components, and Adobe has admitted as much. But here we are almost exactly 1 month later and still no fix. Sad.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded