Disabling Next button and returning to slide leaves it disabled
Sep 19, 2019
In the sample file there are two slides. The first slide has two triggers:
- Trigger 1 - Disable the Next button when the timeline starts.
- Trigger 2 - Enable the Next button when the three buttons are 'Visited'.
This slide works as expected. The problem occurs when you come back to this slide. In the example attached I've included a second slide. After clicking Next, click the previous button and this is what is happening:
- The Next button is disabled even though the three buttons were 'visited'.
- If I click the three buttons again, the Next button is still disabled.
The only workaround that I've been successful with is to change the properties of When revisiting to Reset to initial state. Not ideal as the learner will then have to go through the content again.
This is occurring with both types of players - Modern and Classic.
I'm using SL 360 version 3.31.19951.0. Is this a new problem or has it always been there and I didn't realize this was the expected functionality?
5 Replies
For something like this, you have to make an addition to the disable Next button, you just add conditions to it. Disable Next button if button 1 is not equal to visited, or button 2 is not equal to visited and so on. Here is the example back fixed. It's an extra step but I always like to make my courses reusable for review.
As another alternative (there's always multiple ways to do things in Storyline) you might consider an approach like the attached.
All I did was add "visited" variables for each of your slide layers, default of FALSE, and changed them to TRUE when each layer was visited.
Finally I added a check for your disable NEXT button trigger to check these variables and *only* disable it if any of them were FALSE.
Hope this helps,
B
Thank you both for the suggested alternatives. What's interesting is that David Anderson, director of Customer Training at Articulate, demonstrates using the When: State in one of his courses (Articulate 360: Interactive Learning) on Lynda / Linked In Learning. It is similar to what I have here.
FYI - I went back as far as I could with SL360 (v3.26.18601.0) which is April 11, 2019) and the experience described here is the same. Storyline seems not to be aware of the 'Visited' condition upon returning to a visited slide when using When: States.
For the courses I'm working on now, the best solution would be using conditions.
Thor, that has been my experience as well. Using states to trigger these kinds of things still seems a little flaky sometimes. Variables with conditions much more reliable, especially when you're doing something like revisiting a slide.
Agreed, I tend to use both to cover all bases.
This discussion is closed. You can start a new discussion or contact Articulate Support.