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.
Radu Ghitulescu commented
it would be super important to have this feature and also to be able to link a component specific state from another artboard
Rob K. commented
This would be very helpful and a gamechanger for Adobe XD.
I also agree on the idea that this should work across multiple artboards as well (component on Artboard A can change the state of a component on Artboard B).
Just to clarify, there are two features needed here:
1. Nested components can trigger a state change in the parent component
2. One component can trigger a state change in another, unrelated component on the same artboard
The super feature would be …
A component can trigger an artboard transition *and* change the state of a component on that artboard.
It would be amazing if you could control components with different components.
For example, InDesign buttons allows you to hide other buttons when in action.
If XD could have that ability it would really branch out the depth of how we can create prototypes!
Joshua Holtzclaw commented
Would definitely appreciate this being add in the near future....
felix neoly commented
Creative PEGWorks is a biotechnology company located in the Research Triangle Park of North Carolina with a core business to innovate, manufacture and supply advanced functional polymer products. We manufacture polyethylene glycol, polysaccharide, and polyamino acid derivatives and reagents for research at universities, federal laboratories, biotech, and pharmaceutical companies.
This is so important!!! We need it now! All competitor apps have it.
Joseph Malleck commented
This would be huge!
This is essential. The number of artboards it takes to mockup interactions as a prototype is absurd without this feature. I'm also at a little bit of a loss as to how this isn't already a thing given how standard radio buttons are
Richard Cote commented
This is one of those corners that, after spending a long time setting up elaborate artwork, I am boxed in (again) by XD, stymied by something so obvious you just assume is there, only to discover that it’s not.
It would take me as much time to just code this in HTML/CSS/JS.
Fix this, please!
+1 please this feature is a MUST!!!
Stu Nami commented
I'm trying to prototype a simple web form dropdown menu. I can change the state of the dropdown button and make the submenu box appear. But when I try to make the sub-menu disappear on the second click it doesn't close. So we can only trigger one event at a time I presume? No way to add another interaction to the On Tap event?
Tonny Pettersson commented
Why have you not already done this feature??? is it because you want us to use plugins instead? like Anima?? I dont understand why the basic features like this one will take you 2-3 years to make? You have just made a new "toggle state" feature but you dont show how it works anyway??? I start to consider Figma
It's absurd that this isn't already a feature. Every other modern prototyping tool I've used (all the big ones) already has this, and it's standard and to be expected nowadays. This is a huge limitation.
Erik Gunnarsson commented
To elaborate on my use case, I'm designing a comment feature where I want to use a button to set the state of a comment (adopted as a decision/rejected) and color code it accordingly, add an icon and so on. Another solution to implementing this functionality would be to allow us to set custom click/hover areas similar to invsion. I find myself mostly using nested components to define the input areas, not for repeatability. If this feature was added, I wouldn't have the need for nested components at all.
Erik Gunnarsson commented
This is a must, i just spent an hour researching how to do this as I thought it was an obvious feature. Almost embarrassing that in a tool for UX-designers some of the most natural interactions are still missing.
Alfred Samuela commented
Yes, this would be a game-changer. Please add this as a new feature in an upcoming patch.
Agustín Massolo commented
Change the state of a component (for example a menu) and also by clicking the user is available to change to other section of the platform (change screen)
This is a must.
I'm trying to design a fixed position overlay that appears when hovering over an object within a scroll group. This is not possible as currently the overlay (as a hover state) would have to scroll along with the scroll group.
This would be very helpful feature for larger interface / web design prototypes, as its something that is possible in web development, but not possible to design for here.
There are several ways to implement this - allowing components to interact between each other (eg. if hovering over component 1, triggers a state change in component 2) could also work to the same effect.