I have tried a few times to get my visited state to stay visited, it always goes back to normal as soon as the mouse moves away from it. I even tried adding selected as well-didn't work. I went so far as to watch the tutorial about adding visited states....did exactly what the tutorial said-still didn't work
Hi, I am using the trigger to change the state. I am not sure what you mean by importing the file. i am fairly new to articulate. I am leaving for the day, but I will share it tomorrow. Can I save just that one slide for you to see?
Hi Aviva, do you have your trigger set up to change to visit when the user clicks on the object or when they hover on it? If you are using Hover then make sure the "restore on mouse leave" option is not selected.
If you have the trigger set to change the object or button to visited when the user clicks on it - I would remove the trigger all together as it is not needed in this case.
Hello, I am experiencing the same issue. I am using visited state to make sure the user has visited all the tabs before he/she goes to the next slide. However, due to hover trigger (that I also use in order to indicate where user should click), the tab object goes back to unvisited (i.e. hover) as soon as they (even accidentally) hover the mouse over the object. Could you please help me solve this issue? How can I keep my objects in visited state? :) Tnx in advance!
SL built in states like hover, visited don't need to have a trigger associated with them - so if you have triggers I would try removing them. If that doesn't work can you share the story file or even just that slide and someone can try and help you.
Here's a twist. Same problem, and my buttons initial state is 'disabled.' I need a trigger to change them to 'normal.' The visited state does not stick.
What action changes them to Normal? The beginning of the slide, the learner clicking them, hovering over them, ... ? When you create the trigger, "Change state to Normal" is the action you use, and the answer to my first question is the "When" part of the trigger. After they are in a Normal state, the Visited state will use its built-in superpower to stick, unless you use the Kryptonite trigger on it. The Kryptonite trigger is one that you create that says "Change state to visited ...".
I tend stay away from Kryptonite :) No 'change state to visited...' trigger used.
Usually the action that changes them to Normal is 'when the timeline reaches cue point...' or 'when the timeline ends.' Perhaps another element unknown to Kryptonians?
Thank you for attaching the .story file! Unfortunately, I'm don't see the snag with the button changing back to Normal. In my test, the buttons stay visited. Here's a quick look at my test.
Which version of Storyline are you using? I tested your project using Storyline 360 (Build 3.47.23871.0).
There is a difference, apparently, in how SL2 and SL360 treat Return to Saved State. It shows up here:
In SL2, it actually isn't limited to #5, It affects #2 - 5. When SL360 returns to a layer's saved state, it finds the timeline closed, and merely shows it, which is why Lauren and I didn't see the problem. When SL2 returns to a visited slide, it apparently runs enough of it to initiate the "When timeline ends ..." trigger, which resets the next button in line to normal.
I think you can probably fix it by adding a "if Button 5 state = disabled" condition to all the Buttons.
Yes Walt, not limited to #5. Getting to #5 was one path to see all buttons with the issue. The "if Button 5 state = disabled" is helpful. Thank you!! It reduces the issue. Before getting to #5, though, the issue still exists. I can reduce it further by adding the same condition with, for example, "if Button 4 state = disabled" ...etc., to certain buttons as the layers progress.
Your kindness and knowledge is very much appreciated - Thank you Walt!!
20 Replies
Hello Aviva!
Are you using the built in states, or are you using a trigger to change the state?
Please make sure you are working locally as described here. You could try importing the file into a new file as well.
Also, you could share your file here if you would like us to take a look.
Hi, I am using the trigger to change the state. I am not sure what you mean by importing the file. i am fairly new to articulate. I am leaving for the day, but I will share it tomorrow. Can I save just that one slide for you to see?
Thanks.
You can click on the link above to see how to import into a new file.
Yes sharing just the one slide is perfectly fine :)
Hi Aviva, do you have your trigger set up to change to visit when the user clicks on the object or when they hover on it? If you are using Hover then make sure the "restore on mouse leave" option is not selected.
If you have the trigger set to change the object or button to visited when the user clicks on it - I would remove the trigger all together as it is not needed in this case.
Hello, I am experiencing the same issue. I am using visited state to make sure the user has visited all the tabs before he/she goes to the next slide. However, due to hover trigger (that I also use in order to indicate where user should click), the tab object goes back to unvisited (i.e. hover) as soon as they (even accidentally) hover the mouse over the object. Could you please help me solve this issue? How can I keep my objects in visited state? :) Tnx in advance!
Hi Masa
SL built in states like hover, visited don't need to have a trigger associated with them - so if you have triggers I would try removing them. If that doesn't work can you share the story file or even just that slide and someone can try and help you.
Hi Wendy, I followed your advice and removed the triggers and now everything runs smoothly :) Thanks for your help!
Excellent Masa - so glad you sorted it out and all the best with your project :-)
I just took this advice and it helped too! Remove the triggers and it works!
Great news Ericha - glad it worked for you. All the best with your project!
Here's a twist. Same problem, and my buttons initial state is 'disabled.' I need a trigger to change them to 'normal.' The visited state does not stick.
What action changes them to Normal? The beginning of the slide, the learner clicking them, hovering over them, ... ? When you create the trigger, "Change state to Normal" is the action you use, and the answer to my first question is the "When" part of the trigger. After they are in a Normal state, the Visited state will use its built-in superpower to stick, unless you use the Kryptonite trigger on it. The Kryptonite trigger is one that you create that says "Change state to visited ...".
This post was removed by the author
I tend stay away from Kryptonite :) No 'change state to visited...' trigger used.
Usually the action that changes them to Normal is 'when the timeline reaches cue point...' or 'when the timeline ends.' Perhaps another element unknown to Kryptonians?
If you can attach your .story file here (or at least the relevant part of it), someone may be able to look under the hood, and find the problem.
Timelines have been shortened to view quickly.
After button 5 info is completed, click on the visited buttons. The button to the right will change to Normal.
Hi David!
Thank you for attaching the .story file! Unfortunately, I'm don't see the snag with the button changing back to Normal. In my test, the buttons stay visited. Here's a quick look at my test.
Which version of Storyline are you using? I tested your project using Storyline 360 (Build 3.47.23871.0).
I'm seeing the same thing as Lauren's video.
Well, fiddlesticks, I'm uh... well, uhm... using... Storyline 2.
I have the last build (13: 1804.2716)
Walt & Lauren - thank you very much for your attempts to help!!!!!
Unless you have a suggestion for this build, it appears updating will be my salvation.
There is a difference, apparently, in how SL2 and SL360 treat Return to Saved State. It shows up here:
In SL2, it actually isn't limited to #5, It affects #2 - 5. When SL360 returns to a layer's saved state, it finds the timeline closed, and merely shows it, which is why Lauren and I didn't see the problem. When SL2 returns to a visited slide, it apparently runs enough of it to initiate the "When timeline ends ..." trigger, which resets the next button in line to normal.
I think you can probably fix it by adding a "if Button 5 state = disabled" condition to all the Buttons.
Yes Walt, not limited to #5. Getting to #5 was one path to see all buttons with the issue.
The "if Button 5 state = disabled" is helpful. Thank you!! It reduces the issue. Before getting to #5, though, the issue still exists. I can reduce it further by adding the same condition with, for example, "if Button 4 state = disabled" ...etc., to certain buttons as the layers progress.
Your kindness and knowledge is very much appreciated - Thank you Walt!!