Displaying layers based on 2 different variables
Jan 05, 2016
I'm trying to build an interaction that simulates software in which you have a row and a column number. You can click up or down arrows to change the row or column number from 0 to 5. Once either the row or column number is changed, I want to display a different graphic (layer). It's a test question so in the end I want to judge the learner's answer (say the correct answer is "2 4", meaning Row = 2 and Column =4.
So it's a 2-parter: what's the best way to swap out layers based on the learners input on 2 variables (the harder part, to me), then judge their response when they click a Submit button. See the attached screen grab for what the interface looks like. The 2 by 6 grid (0 to 5) changes based on learner input and different cells appear. I have all of these graphics captured (36 graphics = 6 squared).
Thoughts?
9 Replies
I don't want to have to duplicate all of 76 triggers (both up/down arrows, 36 checking if Row changed, 36 checking if Column changed) on each of the 36 layers. There's gotta be an easier way, right?
Is there a limit of states? Is this something that could be done with states?
Have a look at the attached (rather rough) version. I use a T/F variable as an indicator that some button (either row or column button) has been clicked. Whenever that variable changes, a layer is displayed, depending on row and column number. Using this 'indicator varaible' saves you having to replicate all triggers for each button. For scoring, I use two offstage radio buttons that are set based on the user selection (in my example the correct choice is row=2 and column = 4). This setup does require a few triggers but seems manageable. Hope that helps.
Sorry I forgot to mention that row and column number can be changed with the small blue buttons in the upper left.
Thanks Michael!
So the value of the Something Changed variable doesn't really matter, it's just a trigger to know something has changed and then figure things out? That's the "easy" part I was missing.
THANKS!!!
Correct, the Something Changed variable is just an indicator, it is simply toggled between True and False everytime a Up/Down button is clicked. I thought that using this indicator would greatly reduce the number of triggers, since you are then using slide triggers rather than having to replicate the same triggers for each button. Hope that makes sense.
It does completely. The Articulate Community and you ROCK!!!
Thanks again!
Michael:
Thanks again for your help. It needed a few tweaks but got me well on my way. Here's the finished file if others need to see. There are 3 exercises. The answer pairs are: 1,3; 0,4; and 1,0.
Thanks Mark for sharing the finished file - we always like to see additional examples. :-)
This discussion is closed. You can start a new discussion or contact Articulate Support.