Forum Discussion
"Resume Saved State" is not saving State of Next Button when returning to slide
Hello,
I have a slide that hides the Next button when the Timeline starts, then brings it back to Normal when the users Visits 3 objects (and their States change to Visited). I have the slide set to "Resume Saved State" for when the user returns.
However, when the user does return to the slide, the Next button is still hidden and the user has to click the last object (whose State is still Visited) in order for the Next button to appear. I need the Next button to stay Saved along with all of the other States when returning to the slide. Any help?
Thanks!
23 Replies
Also, I'm using Storyline 3!
Each time the slide loads irrespective of the resume state the timeline start trigger will fire you need a condition to say change next to hidden if object 1,2,3 are not equal to visited
Hi there, Shauna!
Our team is investigating an issue where the next button remains disabled or hidden on a revisit to the slide, even when the slide properties are set to Resume Saved state.
To workaround it while we continue investigating, look at adding these triggers to the slide or the Slide Master:
- Change state of next button to hidden When the timeline reaches 0.5 seconds.
- Change state of next button to normal When the timeline ends, on the condition that the objects are visited.
We'll keep you posted on the issue here!
This worked for me.
Has this issue been resolved? It is a pretty common programming ask from clients (to require users to click all buttons). I programmed my entire course already with the "change state of next button to disabled when the timeline starts" and "Change state of the Next button to Normal when the state of ____ is visited" and did not realize the next button stayed disabled upon returning to the slide. I understand the variables and triggers I can use to resolve this, but I really don't want to have to go back and reprogram every slide. Is there a quicker fix than deleting these triggers and starting over? Thanks!
Hello Ashley!
I'm happy to help! It sounds like there might be something specific in your file affecting the state of the next button.
With your permission, we'll take a look at your project file to investigate what's happening. We'll delete it after troubleshooting. You can upload it privately here: Support Upload Link
When you upload the file, we'll receive a notification. After reviewing the file, we'll get back to you as quickly as possible.
Anything yet on this? I cannot get mine to work using the either of the triggers you suggested there.
Do we need to have a enablenext count variable?
Okay, I looked back at one of my old Storylines from my last project manager, she is a genius by the way with variables and triggers here is what works:
EnableNext1 is the variable and it is set to False.
1st Trigger
Set EnableNext1 equal to True when the state of (enter you object or objects) are Visited
2nd Trigger
Change state of the next button to Normal when EnableNext1 changes if EnableNext1 is equal to True
3rd Trigger
Change state of the next button to Normal when the timeline starts if EnableNext1 is equal to True
Hope this helps!
@Ronda thank you for attaching this fix. I've had this problem in two of my courses for like 3 years. I'm glad to know someone was actually able to create a very solid workaround on this using the variables.
Thank you,
Brian
Thank you, Ronda! Those triggers worked. It should be noted that you also need a trigger of Change State of Next button to Hidden when timeline starts if variable EnableState = False, and it needs to be above the trigger to change it to Normal when all objects are in a Visited state.
Fantastic solution, Ronda! I appreciate you sharing that here. I'm sure it'll help others who find this discussion in the future!
Thank you, thank you, thank you! I was racking my brain to get this function to work and your instructions were perfect. Good job!
I am having this same issue. The variable work around is not as great for me as I have 12 different buttons that need to be in the visited state before the next button can be enabled. Any update on when this issue will be resolved? I need it to resume the state even when the learner returns to the slide WITHOUT them having to click on an already visited button again. Please help.
Hi Tori!
I see that you submitted a support case and are working with my colleague, Lianne! Great call. I encourage you to continue troubleshooting in the case so we can understand the root of the issue!
It sounds like the slide is set to "return to initial state on revisit", as that is what usually causes the timeline to start when returning to the slide. Have you tried setting it to "save state on revisit?"
