10 Replies
Walt Hamilton

Two ideas:

Visited is a built-in state with built in triggers. An object with a visited state changes to Visited when the object is clicked. If you write a trigger to do that, the built-in actions may be offended, and refuse to work . If you want to change the state of that object with a trigger, then you need to use a custom state with a different name.

Also, there is a possibility that Oval 1 is on a different slide than the one that changes HOME. In that case, this trigger won't hear HOME change, because variable changes are heard only on the slide where they change. If the trigger hears the change, it can't change a state on a different slide.

So, change the name of the state, and be sure HOME is changed on the slide where Oval 1 is.

Brian Allen

Agreed... I would definitely advocate for using custom states and avoid using the default (i.e. "visited").

Also, you can get around the need to have Oval 1 on the same slide as HOME by changing your condition from "when HOME changes" to "When the timeline starts on this slide".

This will prompt Storyline to check the value of HOME when the slide loads, and will allow it to set the correct state of the graphic based on that value.


IF your state change is happening on the same slide as the variable change, then "when HOME changes" should work, as long as you're using a custom state.