Best Practice for Next Button Trigger Conditions
Apr 05, 2013
I'm curious if someone has a more elegant way to manage mulitple conditions on the Next button.
Here's my situation:
I have a slide where I ask the user to select their location. There are 18 radio buttons to choose from. I don't want the user to be able to advance to the next slide without selecting one of these buttons. Also if they try to advance without selecting a button I want to put up a warning message telling them to do so. I know how to do this using conditions on the Next button but it seems kind of tedious adding 18 conditions to one trigger saying "Jump to next slide when user clicks next button if button 1's state is equal to visiting,... or if button 2's state is equal to visited, or if button 3's state is equal to visited, etc,. 18 times. And then creating another trigger on the Next button that says show the Warning layer with the 18 conditions on it.
Is there a more elegant way?
3 Replies
Hi Brett,
One way might me to set up a T/F variable - maybe call it SelectOne - default is false
Then, on the slide with the radio buttons, set up a trigger that says:
Action: adjust variable
Variable: selectone
Operator: =Assignment
Value: Value True
When: State
On: Any of
And then in the list, select all the option buttons
Are: selected
This is easier because you can just click down the list bing bing bing bing (18 times)
And for the warning layer, just set a trigger to show the layer when the Learner clicks the next button
And for the Jump to next slide condition,choose "Variables"
If: selectone
Operator: ==Equal to
Type: Value
Value: True
Trigger order should be, top to bottom
Slide Trigger
Set selectone...
Player Triggers
Show layer warning when
Jump to next slide when
Rebecca, thanks for the detailed response. I knew there was a more efficient way to accomplish this and yours certainly is. One of the great strengths of SL is its flexibility; more than one way to get something done. It's also one of its challenges to figure out the most expedient and elegant way to do so.
Thanks again for your suggestion.
Brett
Hi Brett,
I know what you mean about finding the most efficient way in SL...and I know I don't always reach that goal. Glad this was helpful.
This discussion is closed. You can start a new discussion or contact Articulate Support.