In my current work, I need an element to trigger a “scroll to” action while also triggering the “switch to” action.
It is very common for us to need to swap the state of the triggering element (to show that it has been “clicked”) while also triggering the actual action.
Currently, you can’t do that.
I suggest merging this with Prototyping | Conditional logic & variables - #36 by Pete_Markiewicz
The feature requested will require some form of variable management. Both discussions are attempting to call out the same missing feature, which isn’t so much about multiple events per trigger, but about allowing the end user to create a custom namespace for component state control.
Component-independent state control is a feature that can be built within the confines of the Figma UI as it is today. See Prototyping | Conditional logic & variables - #23 by tm_prof_rs for a suggestion.
In my current work, I need to trigger a “liked button” click to change the icon from outline to fill and also display a dialog.
Adding myself to the list of people that really need this feature to exist!
As a newbie I went around a cack handed way of multiple variants opening and showing a change state of a button. This is ridiculous I thought there must be a way to do a simple overlay AND show the change state of the button clicked. Of course I’ll learn about overlays and…….hold on a minute. I can’t…but it won’t. This can’t be the way.
Did you notice that we lose the ability to put a second click on a surrounding frame/level ?
I need this as well. Strange that this isn´t possible.
figma, you only need this one step to take over all other prototype apps…
Please add the chain trigger already. be sure to add control over other component status too
Once again just ran into the need of having multiple interactions on the same actions (Example, On Button Click > Close Modal and Swap Radio Instance to Selected)
This is the biggest feature that I need. Multiple triggers of the same type on one component that do synchronous or a-synchronous actions. I understand that this may reduce Figma’s simplicity - but the benefits for veteran users will be phenomenal!
Example could be - when creating a trigger of the same type (on click for instance), it will group them together. You could select the group and it may have an options for synchronicity of the actions. Imagine you have a map application prototype and there is a button called “zoom to location” - which will have 2 on-click triggers.
- 1st on click - ‘Scroll to’ which scrolls to the scroll-to element on the map in the frame
- 2nd on click - ‘Open overlay’ which opens an overlay on the frame, displaying the location details.
If set as Synchronous - which will first scroll, and then open overlay after scroll has finished.
If set as A-Synchronous - it will scroll and open overlay at the same time
P.S. I am prototyping this at the moment and having a very difficult time doing this without hacking a bunch of screens. Very easy to do in Axure, but we are using Figma at the current workplace.
This would be so useful for advanced prototyping. Please add this feature!
I also am coming from Axure and this is a HUGE issue for me right now working on a mobile app prototype. If we could get conditional interactions like Axure that would be PERFECT.
Please, add this feature!
Agree, I have a problem creating multiple interactions on the same action. For example, when I create a “tap” interaction, I want it to change it to a variant and at the same time scroll to the section that I want. I can’t do that without making many frames!
Thy would Definitely be a GREAT feature, enabling much more realistic prototypes. I have at least 2 projects right now where I’d use it.
Axure was already able to do multiple interactions on one trigger more than a decade ago. I really do wonder why Figma still can’t do this. It would be so helpful in many projects.
Figma is an awesome piece of software. But in this regard Axure is KILLING you with unlimited actions per click. I REALLY need multiple actions per click… it’s very easy to make nice pages and layouts in Figma but very hard to prototype complex interactions.