Restricting NEXT button with variables vs. states
Nov 24, 2015
We just upgraded to SL2 and are finding some issues with how we handle restricting the use of the NEXT button. In the past, we created a "Click Next" shape-based prompt that's initial state is set to Hidden. When the timeline ends or the user completes the necessary interaction, the state changes to Normal. We then created a trigger to jump to the next slide when user clicks NEXT if "Click Next" is Normal. With me so far? Okay.
With the SL2 upgrade, that no longer seems to work. Instead, I found that if I create a T/F NEXT variable (default to FALSE) that changes to True when the timeline ends or the interactions are completed, that seems to work. Unless I'm overlooking something, that seems awfully redundant to me.
So my question is...any reason I can't seem to trigger off of a changed state?
2 Replies
Hi, Jason -- Thanks for your question, and if I am understanding correctly, you may want to take a look at this information on How to Temporarily Hide or Disable Navigation Buttons and let us know if that will do the trick for what you have in mind.
The change in a state is broadcast only to the slide on which it changes. if it is changed while a user is on a content slide, it is not announced when they return to a navigation slide.
When states are changed (or in a certain state) seems to work best in conditions. they don't work well as a means of initiating a trigger.
This discussion is closed. You can start a new discussion or contact Articulate Support.