15 Replies
Brian Allen

Hi Anne,

I agree working with image states this way can be a little quirky sometimes.

First, storyline will automagically set the image state to "Visited" when clicked, so you do not need the first trigger in your panel.

Second, sometimes I have trouble going back to the "Normal" state via a trigger, so what I do is duplicate the Normal state to create a custom image state, then target that custom state with my trigger.

So I would do something along the lines of "change image state to "CustomState1" if image state is equal to "visited"".

Phil Mayor

"Normal" is a strange state as far as storyline is concerned particularly if you use selected or visited. Often an object that is selected/visited will also validate as normal, this is because the built in states are hierarchical and are all inherited built upon Normal, much better to follow Brian's suggestion and use a custom state

Bruce French

I found that it seems if what you click to change state is also in the new state then you can click it again to go back. If your new state is completely different it doesn't seem to be able to set a trigger to go back. I've been intending on experimenting with invisible boxes over the top to act as a trigger for things like that. I've not got around to it yet though but I can't see why it wouldn't work.

MeShell Mortensen

Okay, I have grouped objects on a free-form question slide. They have a normal and a selected state. They automatically move from normal to selected when clicked, but I am unable to get them to move back to a normal (or even Deselected) state. These are possible answers to the questions so I need them to deselect, any ideas?

Ashley Terwilliger

Hi MeShell,

If you're having trouble with the state of your objects and you're using triggers, it would help to have folks in the community take a look at your .story file.

Are you able to share a copy of your file with us? If so, you can upload at this link using the Add Attachment button or you always have an option to share privately with our Support Engineers. Either way, we'll delete it when done testing.