Right now, you can already accomplish these by combining conditional statements with the “After delay” interaction, but it is extremely tedious to maintain and demands a lot of janky component work (see example of implementation in video).
Simply having “Listen for change in variable X” as an interaction would be a really powerful tool to create reusable components for advanced prototypes.
Thank you for providing feedback! I will share this with our internal team. Your input is highly valued, and we will take it into consideration for future enhancements.
I made a post about this some time ago, but I completely agree. I have also solved this by creating “After delay” components that run constantly. My project is very large, and this results in it being very CPU intensive, and the prototype interaction lag as a result. “Listen for change in variable X” might not be enough, because you might need to listen to several variables. So, it would be better to listen for any change, in any variable. “Listen for change in variables” would solve my needs at least. Aka, OnEvent/EventUpdate.
It is also very tedious not being able to copy and paste elements within an event.
No, I don’t think this is the same functionality. Binding a variable change to an action is not the same thing as binding a variable change to an event.
It is interesting how little this is voted on. It’s one of those things that most designers wouldn’t think to want or know about and are probably okay with recreating the same prototype conditions over and over to each action, while devs have it drilled in their head to keep things DRY and have a concept of listeners so that we only have to write the listener conditions on the targeted element (e.g. undisable the submit button when checkbox 1, 2, and 3 are checked). As both a designer and dev like a lot in the comment probably are, this is hurting my soul, and I think it’d hurt designer souls too once they understand how much cleaner and less tedious this could be (wouldn’t take much, imo).
