Changing button state when an expected action is NOT completed

I have two sets of buttons:  Set 1 and Set 2.  When a learner clicks on a button in set one the state of that button changes to "Selected."  If the learner then clicks on the button in Set 2 that matches the selected button in Set 1 both buttons disappear.  That is working fine with triggers thanks to Jeanette Brooks' help.

What I want to do now is have the selected button in Set 1 return to the Normal state if the learner clicks on an incorrect button in Set 2.  Right now the learner can select a button in Set 1 and then simply click each button in Set 2 until the matching button is selected and then both will disappear (state changes to hidden) because the selected button in Set 1 remains selected.

What I'm hoping to do is create a trigger that says, "When button A in Set 1 is selected and any button in Set 2 other than button A is selected both buttons return to the normal state."

I can think of a couple of ways to do this but they require a lot of triggers.  I'm trying to find a more concise way of accomplishing the desired result.

5 Replies
David Anderson

Hi Steve,

Can you check out this sample that Gerry put together during the beta. It actually uses Storyline's built-in drag-drop interaction to manage the shuffling.

I updated the first four tiles to include State and City so you can test the interaction. This is probably the best way to approach your interaction. But like you said, it will require a handfull  of additional triggers

Steve Shoemaker

Thanks Dave, this works great!  This is actually how I planned to approach this when I first started the project (setting variables based on which tiles were clicked and then comparing the variables).  Jeanette suggested using button sets and that worked fine too but then I had the problem of returning the buttons to normal state when incorrect matches were chosen by the learner.  I never even thought of making a disabled state that is identical to the normal state.  That's brilliant and I'm actually mad at myself for not thinking of it!

It's an awful lot of triggers on each rectangle but the end result will be worth it.  The only problem is that when I demonstrate this to the faculty senate I'll have 100+ faculty members wanting the one (me) instructional designer to do something for their classes!