Forum Discussion
No NEXT Button When Click PREVIOUS
Hello, Oh Great and Powerful OZ...
I have 3 bullet points on a slide.
- I created 1 cue point to pause the timeline after bullet point #1 layer has been visited and a second cue point after bullet point #2 has been visited.
- The 2nd bullet point and button would only appear after the learner clicks on the first bullet point button and closes the 1st slide layer (resume timeline here).
- The same would apply to the 3rd bullet point and button appearing after the 2nd bullet point layer has been closed (resume timeline here).
- After the 3rd bullet point and button layer is completed, the NEXT button appears and allows the learner to advance to the next slide.
All goes extremely well until (dramatic pause) advancing to the next slide and then clicked PREVIOUS to go back to the slide with the cue points (you KNOW someone will click PREVIOUS at some point). The NEXT button will not enable, so the learner can advance again to the next slide. I have:
- Set state of NEXT button to "Normal" after all layer buttons have been visited.
- I have also tried to set the slide to "Resume saved state" when slide is revisited...this did not work either.
- Tried using object states as a trigger to get the NEXT button to display when revisited, nada.
Unfortunately, the Storyline 360 course is proprietary, so I am not able to post the Storyline file for your astute observation.
I have been looking at this too long...What am I missing?
It sounds like you have a trigger that disables the Next button when the timeline starts. That trigger runs when returning to the slide.
Since you don't want it to run if the user returns to the slide after viewing all the layers, you need to add a condition to prevent the trigger from disabling Next again.
Here's an easy way to do that:
- Create a T/F variable with a default value of False.
- On the last layer, add a trigger that changes the value of the variable to True.
- For the trigger that changes Next to Disabled, add a condition so it only runs when the variable =False.
If that's not the problem, well, further troubleshooting is just guessing without seeing the .story file. If you upload it, someone might be able to solve the issue.
Here are the best practices for uploading a .story file:- Only include slides that are related to the problem. In this case, that would be the one slide with the problem.
- Be sure objects, layers, motion paths, and variables have meaningful names.
- If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.
Judy,
Huzzah! Thanks for the insights.
I do have a trigger that disables the NEXT button when the timeline starts.
I will try your recommendations and post further if the recommendations are unsuccessful. I will see if I can provide redacted slides related to the problem.
Hope you enjoy your Turkey (or "Impossible" Turkey) Day...Gobble on...
The demo file attached to this post might help: TIP: Controlling the NEXT Button 101 | Articulate - Community
Happy Turkey Day to you, too.
