Forum Discussion
Triggers Not Working Across Layers
Hi everyone,
I'm working on an activity where the learner takes a self-assessment and then gets custom feedback based on their score. Each radio button changes a variable that adds to the total score, then the feedback appears based on the score they received.
My issue is with the custom next button on each slide. I want to restrict users from advancing to the next layer until they've answered the question on the screen. I'm using a basic slide rather than a question slide because I need custom feedback to appear, but I don't want it graded.
I've set the initial state of the button to disabled, and added a trigger to change the state to normal once at least one of the radio buttons has been selected. This works perfectly with the base layer, but once it gets to Q2 it doesn't work, even though the triggers are the exact same. I've tried deleting and replicating the trigger, as well as the button itself, but it still isn't working and I can't figure out what I'm missing. I can't progress past Q2 to test the rest of the layers, but I'm assuming there are similar issues across all the layers.
Any help is appreciated!
The problem is the trigger on the Q3 layer that's supposed to change the button to Normal. It's looking for one of the radio buttons on the BASE to be Selected.
Also, the trigger is set to change Button 1 on the BASE.
The fix: edit the triggers so they refer to objects on that layer. (I didn't check the other layers, but I suggest you do so.)
BTW, programming and troubleshooting would be a lot easier if you gave buttons meaningful names. For example, Q1-response1, Q1-response2, Q1-response3, Q2-response1, Q2-response2, Q2-response3, etc.
3 Replies
The problem is the trigger on the Q3 layer that's supposed to change the button to Normal. It's looking for one of the radio buttons on the BASE to be Selected.
Also, the trigger is set to change Button 1 on the BASE.
The fix: edit the triggers so they refer to objects on that layer. (I didn't check the other layers, but I suggest you do so.)
BTW, programming and troubleshooting would be a lot easier if you gave buttons meaningful names. For example, Q1-response1, Q1-response2, Q1-response3, Q2-response1, Q2-response2, Q2-response3, etc.
THANK YOU! I figured it was something simple that I was missing. I'm usually too lazy to name all of my objects, but I think this finally convinced me to start. Thanks again!
You're welcome.
This is a perfect example of why it's worth the time to rename objects. So, yes, start doing that. You'll thank yourself for it later. 😁
