Highlighted

New instances of component states are inheriting text of master.

New Here ,
Sep 02, 2020

Copy link to clipboard

Copied

Hi,

I have  alot of identical buttons in my design. The intuitive way to work with this is to create one button, give it the required states and then set it as a component so I can instance it for all the other buttons. All of the buttons are identical except for the text. 

 

The issue is that when I duplicate the button and change the text in the default mode, that change does not carry over to the other states. 

I make a new button, the label says 'Cheese', it has a hover state where the colour of the text changes. I covnert this to a component. 

I then use the component to instance another 'Cheese' button but this time I change the text to 'Meat'. When I hover over this new button the default state says 'meat' the hover state says 'Cheese'.

 

I have to edit the label and each state of the label for every instance, this seriously defeats the point of instancing a button in the first place and given that I have to manually activate the state, edit the label, deactivate the state for every single instance it is ridiculously time consuming. It would be faster to build this in CSS than is it to work in XD. 

Adobe Community Professional
Correct answer by Spas K. | Adobe Community Professional

"It would be faster to build this in CSS than is it to work in XD."

Yep. It's why I avoid using hover effects altogether, as the fidelity isn't worth the time wasted, unless it is some small interaction that I need to demonstrate.

 

The whole component states thing was either rushed or not thought out completely, so we are stuck waiting until the dev team decides to fix it.

 

It seems Xd mostly aims to satisfy the needs of Mobile app designers, who don't really need the hover thing, rather than us web designers, where it is an essential feature.

Views

50

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

New instances of component states are inheriting text of master.

New Here ,
Sep 02, 2020

Copy link to clipboard

Copied

Hi,

I have  alot of identical buttons in my design. The intuitive way to work with this is to create one button, give it the required states and then set it as a component so I can instance it for all the other buttons. All of the buttons are identical except for the text. 

 

The issue is that when I duplicate the button and change the text in the default mode, that change does not carry over to the other states. 

I make a new button, the label says 'Cheese', it has a hover state where the colour of the text changes. I covnert this to a component. 

I then use the component to instance another 'Cheese' button but this time I change the text to 'Meat'. When I hover over this new button the default state says 'meat' the hover state says 'Cheese'.

 

I have to edit the label and each state of the label for every instance, this seriously defeats the point of instancing a button in the first place and given that I have to manually activate the state, edit the label, deactivate the state for every single instance it is ridiculously time consuming. It would be faster to build this in CSS than is it to work in XD. 

Adobe Community Professional
Correct answer by Spas K. | Adobe Community Professional

"It would be faster to build this in CSS than is it to work in XD."

Yep. It's why I avoid using hover effects altogether, as the fidelity isn't worth the time wasted, unless it is some small interaction that I need to demonstrate.

 

The whole component states thing was either rushed or not thought out completely, so we are stuck waiting until the dev team decides to fix it.

 

It seems Xd mostly aims to satisfy the needs of Mobile app designers, who don't really need the hover thing, rather than us web designers, where it is an essential feature.

Views

51

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Sep 02, 2020 0
Adobe Employee ,
Sep 02, 2020

Copy link to clipboard

Copied

Hi Ben,

 

Thanks for reaching out and sharing the feedback. I completely understand that there is a scope of improvement in such workflow so for sure, I'll share this feedback with the Engineering team and you can do that too by upvoting this request: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38973007-allow-com...

 

This is the best way of communicating with the Engineering and Product Management teams regarding issues and suggestions so they can be implemented in future releases. 

 

Regards

Rishabh

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 02, 2020 0
Adobe Community Professional ,
Sep 02, 2020

Copy link to clipboard

Copied

"It would be faster to build this in CSS than is it to work in XD."

Yep. It's why I avoid using hover effects altogether, as the fidelity isn't worth the time wasted, unless it is some small interaction that I need to demonstrate.

 

The whole component states thing was either rushed or not thought out completely, so we are stuck waiting until the dev team decides to fix it.

 

It seems Xd mostly aims to satisfy the needs of Mobile app designers, who don't really need the hover thing, rather than us web designers, where it is an essential feature.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 02, 2020 1