Disabling Next Button Until All Layers are visited
May 30, 2018
OK...I'm stumped! I've been scouring these help boards and have followed the directions but I still can't get my training to work. I have 5 buttons that I want users to visit before they can get to the next slide. I have a trigger that adjusts the variable of layers complete when the value is true when the state of all buttons are visited. I also have a trigger to jump to slide on the condition that layers complete equals to true, yet the next button is fully accessible right away. I've attached my file for review. It's slide 1.21 as well as 1.30. Thank you!
8 Replies
The course is set to restricted navigation and the next button becomes available when the timeline ends. So you need to have a way to disable and enable the next button based on user interaction.
Also, in the future, I'd only send the one or two slides so people don't have to download a big file.
Thank you Tom! I took the restriction off the navigation to experiment a little. I added a trigger to adjust the variable of layers complete to the value of true when the state of all buttons are visited. And added a condition to the "jump to slide" trigger of layers complete = equal to true and it's still not working. Yet a previous slide I have has the same concept...the triggers are exactly the same and it works.
It is maybe not a well-known, but newly known bug (See Ashley's first Reply) in SL that using "State of XXX is ..." in a When statement only works if you have only three or four triggers on a slide. It seems like a wonderful idea, but more triggers than that, and it just doesn't work. (Note: this restriction doesn't apply if State of ... is used in the Conditions part of the trigger.)
You need to set the when clause of those triggers to fire based on an actual event (like "When timeline starts", or "When user clicks", or "When variable changes")
Just a clarification to that mentioned bug, it's only happening when you are adjusting a variable based on that state of 5 or more items being equal to X, and that'll cause the variable to not change. You can absolutely have that many triggers on a slide, and even a lot more!
Thank you Ashley! It seems to be that is my issue. The one slide it works on only has 2 items, where the slide it's not working on has 5. Is there a work around on this? Is there a time frame when this "bug" will be fixed?
Hi Karen,
Variables are more useful when you need to keep info between the slides. In your case I recommend a simpler approach, using condition and states.
Attached, I am sending the 1.21 corrected without variables. It worked.
Also, I included some animation, hope you like it. ;-)
Thanks so much Eduardo! I love the animation! I'm somewhat new to building these courses so still learning some of the little tricks! Looking forward to adding it into my full training!
This discussion is closed. You can start a new discussion or contact Articulate Support.