Forum Discussion
Visited and Selected States in Storyline
I am once again asking Articulate to change the stupid built-in function that both selected and visited states are enabled at once. That makes zero sense. Why would you need a visited state when you're trying to present a selected state. No one should have to waste precious time to create many triggers to do what Articulate can easily just change about this function.
Visited states should only be enabled when another object is selected after the previous object has been selected. It's really that simple.
5 Replies
I know this is an old post but this has me pulling my hair out. It certainly doesn't only affect you. I want the user to see which button they are ON, and then want them so see which buttons they have already SEEN. This is logical. Why is there not a built-in way to do this??
This can be done with a visited and selected state and button sets
Nobody. Don't expect an answer as this is not a question; it's a rant that seems to affect only you.
Nobody, huh?
