Enable Next Button at Revisit
Feb 07, 2017
Greetings:
I have search on the e-Learning Heroes site to find a resolution to a roadblock I am running into. However, I found a discussion, but it there was not much that I can use to enable the next button.
What I am trying to accomplish is allowing the learner to revisit a slide and have NEXT button to be enabled, so that they can advance at any time during the review of the slide(s). I am currently using the SL Player – Settings: Free
I do not want the slide properties to be set at "Resume at Save State" because I would like the audio to automatically play when the learner revisits the slide.
Any assistance is greatly appreciated.
I am unable to add the .story, I keep getting page does not exist once I update the discussion (when .story is attached).
10 Replies
Hi Jeannie
do you have a trigger to disable/hide the next button? Free menu means they can move freely through the course.
Hi Wendy,
Thank you responding.
I have the triggers to disable/normal the next buttons. - detailed triggers below.
Triggers:
Change state of next button to Disable when timeline starts
Change the state of the next button to Normal when timeline ends
trying to figure out how to enable the Next button upon revisit. Variable I used did not work even though I selected to adjust the variable to true.
Hi Jeannie,
You can use a combination of triggers and variables. On the slide following the slide you are working on, set a variable and a trigger to adjust that variable. I usually set the variable name to Slide X visited. I then set a trigger on that slide to adjust variable, Slide x visited, to true when timeline starts. Then go back to the original slide, and add a trigger to change the state of Next button to normal when timeline starts with the condition that Slide x visited is true.
I hope this helps!
Hi Jeannie,
We've had some issues today with loading files here into the E-Learning Heroes forums, so I'm sorry you've run into that! If you'd like to share it with our team to take a look at the file in question you can upload using the form here. You could also look at sharing a link to another download location where the file is saves such as Dropbox.
Hi Ashley,
Thank you for the tip. I have created a case and got a quick response.
I have rec'd instructions and a sample of how I would like the course to behave as far as enabling the Next button after revisit. However, it appears it works for the first slide, but for the remaining slides the triggers and variable used does not show the Next button disabled. It appears to be enabled. When the Next button is clicked on, it does not advance (and that is ok because the triggers/variable are working); but I would like to have the course look consistent with the Next button appearing disabled at first preview.
Any recommendations is greatly appreciated.
Since there were issue with uploading a .story file not sure if it is still an issue (will try). If it does not work below are the triggers, variable, settings, and properties used:
Adjust the variable
SlideVisit1
=Assignment
Value True
Timeline ends
Object
Change state of
Next Button
Disabled
Timeline Starts
Object
Condition: Slide Visit
==equal to
Value
False
Change state of
Next Button
Normal
Timeline ends
Object
(would like to keep this property so that audio replays at revisit)
Slide Layer Properties
By User
Reset to initial State
Storyline player: set to restricted.
Regards,
Jeannie
Hi Jeanne
its because you are using one variable called 'slidevisits' - once it is changed to true on slide 1 it's true and your trigger on Slides 2 and 3 are change state of Next to disabled when timeline starts if slidevisits is false but slide visits = true
Hi Wendy,
Thank you for responding and for the information. Does that mean that I would have to create "X" amount of 'slidevisit' variables for each slide I want this behavior work?
Jeannie,
Yes, you would have to create a variable for each slide that you want this behavior.
Thank you Ashlee! This really helps a bunch!
You're welcome! This is something that I had issues with at first. Once you get in the hang of setting the variables, triggers, and conditions, it goes pretty smoothly and a lot quicker than you would think.
This discussion is closed. You can start a new discussion or contact Articulate Support.