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.
Andrew Freire commented
Yes please! Expecially a parent component. Like I have a Menu that I want to toggle open a side menu on tap. But I have to set clicking anywhere on the entire menu to trigger the interaction because I can't just place the listener on the hamburger menu icon..
Cameron Smith commented
Yes please! Was just trying to figure out if I can do this. Would be very very helpful.
please, add this feature. Really useful. I want for example have a component that hovering can show me a textbox, it is useful allow this.
YES that would be amazing and that would actually make sense... I mean that's how it is on a website so why not in XD ?
Ahh I just asked about something like that earlier as I don't want to make a bazillion artboards to simulate that..... do it, Adobe!
Jo yal commented
This will be useful to implement a 5 star rating interaction.
Clicking on the 5th star will light up all other 4 stars also.
Currently, this is not possible.
Saman Salehi commented
This is not a feature... This is an absolute must!
Josh Oberst commented
How is this not a thing?
Not having this feature it makes prototyping anything but the simplest UIs very difficult. I was honestly shocked it wasn't already part of the product.
Yes, please implement this asap. It's such an essential feature in order to build a functional prototype for a desktop app.
Andrew Hart commented
I suggest this is done by adding the ability to Trigger a component state change when another component on the artboard changes state.
I have already made a request to allow a component to change state based on a Time event, so both requests could be grouped into a general upgrade to the component state change trigger mechanism.
I would love to be able to to handle an object behavior from another one.
Examples : Tap an icon to change another component state or to reduce the opacity of a layer... etc..
It would decrease the number of artboards we use in our designs and simplify our work.
Please add this feature. This is necessary for prototyping.
Please do it. I find it hard to believe that it's not already available. Other products have been able to do it for years. Without it, changing states is almost useless unless it is only the simplest of toggle switches.
Honestly, people know what a toggle switch looks like when it's on vs off, and people know what checkboxes look like when on vs off, so that is something you really don't need to prototype on its own. It's a lot of extra work with almost no reward.
Now, what ELSE happens when you turn something off or on, THAT is what matters and why you need to be able to show state changes. Otherwise, state changes are kind of unnecessary, or at least superfluous.
Please do it ! 🏆
I wanted to have an image with hotspots on which I can clic to show an info box. I can achieve that with states and shapes but if I wanted to use a component instead of a shape to have the hover effect, it wouldn't allow me to select a state, only another page.
Bartolomeo D'Alia commented
Absolutely a needed feature!!
It will saves a lot of time!
I have Component A and Component B, both with 2 States.
I would like to click on Component A and switch from State 1 to State 2. But in addition I want wire Component A with Component B and switch Component B from State 1 to State with the same click (on Component A)
-> Click on Component A should change not only the own State but also the state of another component.
Regardless of the artboard - Click on artboard 1 on Component A it should open artboard 2 and already change the state of Component B on artboard 2 to a defined state.
Sarah Sorensen commented
Yes please, this would allow me to eliminate the number of needed artboards
Yes!!! Can only imagine how many artboards I'd be able to cut from my prototype by encapsulating many interactions within a single board vs trying to manage countless combinations of boards and flows. Would be great to be able to go beyond happy path prototyping with XD and I think this feature would go a long way to unlocking that potential.