Next Button

There is no .story file attached.

Hey Greg!

Without the .story file, all I can suggest is to ensure that SL2 is not 'resetting to initial state' the slide in question.

Cheers.

Try again

Hey Greg - see attached.

You can achieve the same outcome with variables instead of states, and conditional triggers.

Cheers,

J

Thanks Josiah it works.

I did try your solution, with one difference which I can now see was the key factor.  As part of my trigger under When, I selected "Variable Changes" and the variable name. Timeline Starts makes much more sense.

Once again thanks, lots of frustration resolved

Hi Greg,

Glad that Josiah was able to assist you here! Using the "when variable changes" trigger is one that can be a bit tricky as it's looking for the variable change to occur at that moment and on that slide to execute the trigger - so if you've changed the variable on another slide or section of the course, that trigger won't execute as the variable has already changed. 

Hope that helps clarify the trigger set up. 

Thanks Ashley, makes perfect sense.

For general information, I changed the trigger from a numeric value to a true/false value as per the screen shot, which ensures the learner visits each module. The initial value of the variable is false. This trigger must be placed before the 2 triggers to change the Next buttons state. The numeric value would have reached its trigger limit prematurely if a learner visited the same module more than once.

Thanks for sharing that here Greg - always good to see another example of how someone has set this up. 

Hi Greg,

Just wanted to chime in on this one. You shouldn't need to redo with variables. The states approach will work (and keep things a little simpler).  

What was happening with your files is that it was partially trigger order and partially the trigger itself.  

You had a trigger to hide the next button when the timeline starts. This was below the trigger that was evaluating the visited states.  So even if the each of the objects has a visited state, that trigger to change the next button to normal will be overridden (when you return to the slide) by the next trigger which says to hide it when the timeline starts.

So the solution is to add a set of conditions onto the 2nd trigger as well. So we add some conditions to that trigger that basically say to change the Next Button to hidden when the timeline starts if any of those buttons are not visited.

I hope this helps!

Mike