Skip to content
← Adobe XD: Feature Requests (Read-Only)

Request details

Adobe XD: Feature Requests (Read-Only): 02 : Prototype mode

Categories

(thinking…)

Allow components event to change states of other components

New states feature is excellent but restricted for self components interaction. In many cases, especially in web and desktop apps, there are cases where a component event should affect another element on screen.
It would be a super powerful option to allow a component event to change states of another component.
Currently if i use component A inside component B, i can't use A to change state of B, even though A is part of B.

956 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

Yoav shared this idea  ·   ·  Report…  ·  Admin →

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
  • Fabio commented  ·   ·  Report

    Absolutely required for design of interactive user interfaces.

  • Kevin Middelbos commented  ·   ·  Report

    Coming from other prototype tools such as Axure, I really miss being able to target other components through Interactions and change their states.

    In fact, I think it's crucial for me (and many others) to create more complex prototypes without having to jump through hoops and maintaining many duplicate artboards to achieve the same (or a sub-par) result.

    Simple example:

    I have two components. The first being a collection of tabs. I want each of the tabs to target a separate component (either on the same artboard or on other artboards) and have it switch to a state of my choosing.

  • Patrick Gibbs commented  ·   ·  Report

    Absolutely required for design of interactive user interfaces.

  • Craig Palenshus commented  ·   ·  Report

    Maybe this feature is too difficult for Adobe to figure out, but it sure would be nice if they would at least provide some sort of an update for why they are ignoring this feature request.

  • Robb Cabansag commented  ·   ·  Report

    This feature would make quick work of commonly used elements such as, tab groups & accordions.

    Seems a basic feature to implement & highly useful for streamlining the prototyping process.

  • John Posey commented  ·   ·  Report

    This feature is desperately needed. Adobe XD needs to become a more robust wysiwyg prototyping tool to be able to create user interfaces.

  • Hasan Demircioğlu commented  ·   ·  Report

    i was searching about that issue and i am here now. It is still not avaliable :(

  • Andrei I. Gere commented  ·   ·  Report

    Very surprised this isn't possible yet. I have been trying to get a checkbox to toggle the state of its label text (which is a separate component with its own hover and active states), as you would expect in any application, where you can toggle a checkbox by either clicking the checkbox or its label.

  • Amir commented  ·   ·  Report

    At least give us an answer why there is no option to do that. I need to go through each state in the component and change all. Very frustrated.

  • Julie Jacob commented  ·   ·  Report

    This is vital. States are useful only if they have the ability to interact with and impact the surrounding and vice versa. Please implement this!

  • MR. Gray commented  ·   ·  Report

    3 years and still nothing on this :/ We are debating on moving to another program just because this hasn't been added.

  • Varun Singh commented  ·   ·  Report

    I agree, this feature would be incredibly useful. Another use case is when you are making a feature carousel: you have different states for different slides in the carousel and would like the button to change the state of the carousel.

  • Anonymous commented  ·   ·  Report

    We seriously need this feature. Having to create an entire new artboard just to change something on a screen upon clicking a button is ridiculous.

  • Ivan Vladimirov commented  ·   ·  Report

    The easiest workaround is to hit Ctrl + G on the inside A component, to place it in a dummy group, and than you can change parent B state using the group.

    The problem is when you have another complex, nested component C, inside A. Than you do not have easy time changing state of B by clicking C.

    I vote for this feature too, to have more flexibility to change one component state from another. For example, give component B a name, so you can reference it.

  • Emily Christmas commented  ·   ·  Report

    In case anyone is struggling with this, I've just ungrouped the element from the component within the component to allow of prototyping within a single component. It doesn't effect the component elsewhere. May not be a viable solution for all instances, but it worked easily enough for me.

← Previous 1 3 4 5 6 7