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.
Patrick Gibbs commented
Absolutely required for design of interactive user interfaces.
Craig Palenshus commented
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
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.
Dylan Maxwell commented
A game changer for prototyping.
John Posey commented
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
i was searching about that issue and i am here now. It is still not avaliable :(
Andrei I. Gere commented
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.
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
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
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
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.
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.
Thomas Gautheron commented
Pretty please, we need this feature!
Ivan Vladimirov commented
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
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.
Everaldo Amorim commented
It would bring XD to the next level!
Mr. D commented
We need this
Ondřej Regál commented
I am also looking for this feature now! Please add this :)
Vincent Monmaur commented
This would allow XD to compete with tools like Axure which lets any interaction affect the state of any components (dynamic panels in Axure).
To this day, XD is not a prototyping tool. It is a UI design tool that lets designers demonstrate some animations or some behaviours on their canvas instead of using word specs. But apart from links, simple hovers and overlays, it is not suited at all to prototype even simple interactions such as carrousels. The duplication of artboards for that purpose is just an horrendously bad practice. Components are there. States are there. Interactive behaviours need to happen at this level.
Jonas Hartmann commented
This would we a game changer for prototyping. right now im trying to set up a menu with really big hover elements which cover other navigation elements, which is almost impossible to set up with what we can do right now.