New and returning users may sign in

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
← Adobe XD: Feature Requests

Request details

Feedback

Adobe XD: Feature Requests: 02 : Prototype mode

Categories

  • CATEGORIES
  • All ideas
  • My feedback
  • 01 : Design mode 1356 ideas
  • 02 : Prototype mode 368 ideas
  • 03: Share mode 46 ideas
  • 04 : Sharing on the web 214 ideas
  • 05 : Asset exporting 154 ideas
  • 06 : Extensibility 37 ideas
  • 07 : Integration with other tools 117 ideas
  • 08 : Mobile (iOS) 25 ideas
  • 09 : Mobile (Android) 18 ideas
  • 10: Developer Handoff 138 ideas
  • 11: Plugins 134 ideas
  • Other 102 ideas

(thinking…)
  • Searching…

    No results.

    Clear search results
    • Adobe XD: Feature Requests 2,836 ideas

Component states to inherit interactions from master default state

Component states should behave like component copy instances. This includes interactions to be copied to all child states. This is essential, for example, for a menu component in which each state is the active status of each menu item. But when I create new state it loses all interactions. Maintaining 5 states with 5 menu items becomes tedious.

71 votes

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Harun Alikadić shared this idea  ·  November 12, 2019  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →

How important is this to you?

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
Tweet
  • Remove
Attach a File

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • bbhoff commented  ·  May 24, 2022 09:00  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Boggles my mind that this still isn't a thing. Every time I start making button components then try to use them across layouts I start to tear my hair out. It's so miserable.

    Submitting...
  • Jens Klang commented  ·  March 23, 2022 03:15  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I found a workaround that I wanted to share. Maybe this solves your high-fidelity prototype problem.

    As in my previous post, the navigation is made on a separate component with just one state. We call that Navigation. Place that object inside the actual Menu object and navigation will be inherited between the states.

    But this only works with navigation between artboards and not states.

    Submitting...
    •  
      Screenshot at Mar 23 10-51-55.png 122 KB
    •  
      Screenshot at Mar 23 11-11-50.png 102 KB
  • Jens Klang commented  ·  March 23, 2022 02:16  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I just re-discovered that this was not fixed. I was wondering why I made a convoluted solution with a placeholder transparent object about the actual menu. But this is why.
    So the solution is to ad a dummy object above the menu that does only has one state, which is controlling the navigation. And then you have to switch the states on each page where the component is. This works if it's a navigation menu in an app/Webb.
    Adobe, please fix this.

    Submitting...
  • Anonymous commented  ·  February 28, 2022 14:18  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I'm creating a very high-fidelity prototype for an important client, as they want it almost fully functional for user testing/stakeholder buy-in. I have a map component in there with 27 polygons that each have an interaction, so the map component also has 27 states. 27 X 27 = 729.

    I HAVE TO MANUALLY ENTER 729 INTERACTIONS, rather than just 27 interactions to the default state which should copy over to all of the other states. This is crazy. The list of reasons not to use Adobe XD grows every day.

    Submitting...
  • Grant Smith commented  ·  July 22, 2021 05:39  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    New to XD and would have thought this is basic functionality. Please see Sketch for great user example.

    Submitting...
  • Jason commented  ·  April 17, 2021 14:38  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    We need this!

    Submitting...
  • Michael Laugesen commented  ·  April 08, 2021 06:16  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Any news on this?

    Submitting...
  • Holly commented  ·  March 23, 2021 11:27  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    States are basically useless without this feature IMO. I should also be able to change the text of the default state and have it update on all child states.

    Submitting...
  • Fanny.B commented  ·  July 23, 2020 14:01  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Yes, it could be great to have the option "copy the change to chid states". Because for a button, you have to change manually le label for all the states.

    Submitting...
  • digita commented  ·  July 03, 2020 06:55  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Any news? Because there is too much manual work for edit states.

    Submitting...
  • John Vanore commented  ·  April 09, 2020 10:11  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    component instances - update to default state should automatically update non customized properties for all other states. This is currently the behavior in the master component; when you update a property in the default state, and that property has not been customized in other states, the other states inherit the change made in the default state. This behavior is not the same in instances of the component however. Similarly, if I cut or paste from/to the default state, that element should be cut or pasted from/to the other states as well. It works this was in the master component states, but not the instances. It should be a consistent experience, but it's not. The result is needing to make the same change many times over throughout all the states. When you have components nested within other components, the issue is magnified. The time it takes to make these changes quickly adds up.

    Submitting...
  • Rob Lee commented  ·  February 04, 2020 09:52  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I use buttons a lot, if I change the label in the default state, it should change the label across states. I have to update 4 states on every button.

    Submitting...
  • Matthias Ott commented  ·  December 12, 2019 01:41  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    +1! This is super important IMO. It already works for the master component but not for other instances of the component. Also got this feedback in one of the XDI workshops. Great to hear that you are on it! :)

    Submitting...
  • Joe commented  ·  November 13, 2019 10:27  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    + 1 for this! *goes back to wiring states to 100 components*

    Submitting...
  • AdminCisco Guzman (Director, Product Management, Adobe XD, Adobe) commented  ·  November 12, 2019 05:44  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Hi Harun. Thank you so much for posting your feedback. This is definitely something we are working on. We agree that you should not have to manually maintain syncing across states and instances, so we are definitely on it. Stay tuned because it's definitely on its way.

    Submitting...

Adobe XD Feedback : Feature Requests & Bugs · UserVoice Terms of Service & Privacy Policy · Adobe Terms of Use · Adobe Privacy Policy