Forum Discussion
Next & Prev Button question
Hello!
I have a few interactive slides in my course. When a learner tries to go back to an interactive slide, the "next" option is disabled, and they're unable to move forward.
Can someone check my settings and let me know what changes are needed? I'd really appreciate it.
3 Replies
- EricSchaffer-d1Community Member
I believe if you go to each slide that want the learner to view and change the slide menu to resumed saved start it will unlock the Next button when they go back. It won't restart the interaction. That they will need to click the replay button. These setting are the little gear in the lower most right.
Good luck
- NedimCommunity Member
I'm only guessing at the issue since you haven’t provided a screenshot of your settings. But when you open Player Properties, then go to the Menu tab and click on Menu Options, you'll see a setting called Navigation Restrictions.
There are three options available there, and each affects how learners can navigate through the course:
Restricting NavigationIf Free is selected, then the issue is likely related to something else. If possible, please upload a simplified or current version of your file for troubleshooting.
- JudyNolletSuper Hero
Here's my best guess: There's a "Set the state of the Next button to Disabled when the timeline starts" trigger. Then there's another trigger to enable Next when the interaction is complete.
The problem is that a "when the timeline starts" trigger runs every time the user visits the slide. That's true even if the Slide Properties are set to "Resume saved state."
The fix is easy: add a condition (or conditions) to the disable-Next trigger so it will only run if the interaction hasn't been completed.
For example, if the interaction is done when a set of buttons = Visited, the disable-Next trigger would look something like this:
Note: It's more stable to use "≠ (is not) Selected" or “≠ (is not) Visited" as a condition, instead of "= (is) Normal." As Hero Walt Hamilton once put it: like us, every state thinks it's Normal. In other words, Normal underlies the other states, so the "= Normal" condition doesn't always work as expected.