Visited state not working
Jun 02, 2015
By
Tracy Logan
I have three shapes on my screen and each shape when clicked on opens a layer. I've created states for the shapes. They each have a Normal, Selected, and Visited. When I test them, the Normal works (of course!), the Selected works, but the Visited does NOT work. When I click on another shape to open up a new layer, the previous shape stays at the Selected state. Shouldn't this be automatic or do I need to setup triggers for the Visited state to work?
I've included two screenshots:
shapestates.png - this is what I have them setup as.
visitedstatenotworking.png - the order I tested this in is the bottom shape I clicked first, then when I clicked on the shape above, the bottom one stayed blue (when it should change to gray).
14 Replies
Are you able to attach your .story file so we can take a look at it to see what is going on.
I was hoping the screenshots would be enough but here's the one page of the project.
Ok, I would have thought it worked like you were thinking.
But, after doing a little research I found that not to be the case. When you select an object it doesn't actually deselect itself when you click another object, and this is why you are not seeing the visited state unless you click a second time to deselect it.
To make this work you need to create a button set, that way when you select another object it will deselect it because only one object can be selected in a button set.
I updated the file for you to have a look, let me know if this works for you.
Wow! That's awesome that you found that. What a hidden feature that is, but I guess it makes sense. I just did the same thing in my working project. I selected all three shapes, right-clicked and made a Button Set. It worked perfectly after that. Thanks so much!
Glad I could help.
I find helping people on this forum is a good way for me to learn as well. That's why if I can't answer directly I ask for the source file to try and see what is going on and how I can solve it.
Love this simple solution Gary! Thanks for sharing and assisting Tracy here.
I have created a simple drag and drop and I want the state of the target object to change to visited when the correct object is dropped on it. The visited state has a blue border and there is no text in it, but when I drop the object on its target object, only the blue border appears and the text is still visible. Can anyone help me figure out what is wrong? I also changed the order of the triggers but it didn't help!
Hi Sepideh,
The visited state is additive on top of the normal state, so you'll see both states at the same time. Here's a bit more on how built-in states work in Storyline.
To fix this, I deleted the object in the Visited state, and I replaced it with a new object. Now I think it's working how you intended. Take a look at the attachment and let me know what you think!
Thanks Alyssa for taking the time to look into it and apologies for my late reply. It makes sense now!!! thanks again :)
I have a dashboard with buttons that I have created a normal, hover, and visited state for. I want the learner to click the tab, it takes them to another slide, they are prompted to click within that slide and it takes them to watch a video on another slide. When the click the next button to return to the dashboard the state doesn't change. It works on the individual slide in preview but doesn't work in review link. Any suggestions?
Hi, Mindy.
I replied to a similar question here. We can continue the conversation there if you have additional questions.
8 years since first post and I'm having the same issues... Why can't states just work as you would expect them too?
Hello Rob,
Sorry to hear that you ran into this issue.
In some cases, adjusting the existing triggers in the slide can help fix any issues with object states. Would you be willing to share a copy of your project file here or in private by opening a support case so we can take a look at your slide? Please include a brief description of the behavior you're experiencing so we can test your file as accurately as possible. We'll delete it when we're done testing!
Developers are lazy.