Forum Discussion
Variables within triggers not working consistently
- 23 days ago
Yup, the problem is using the same set of variables on multiple slides...
Variables maintain their value until a trigger changes it. So, as I said above, after the variables change to True on the first slide where they're used, they remain True. And that's why the next slide jumps after viewing just one layer. The conditions on the trigger are met before the user gets to that slide.
So, yes, you need different triggers for each slide. For easier programming (and troubleshooting), I suggest using a naming convention that indicates the slide and the layer. And keep the names as short as possible.
For example, the variables on the first slide could be s1_L1done, s1_L2done, s1_L3done, and s1_L4done. The variables on the second slide could be s2_L1done, s2_L2done, s2_L3done, and s2_L4done. And so on.
Sorry, I was trying to figure out how to locate the .story file. I've included it here.
Your first solution sounds like it may be applicable... So, on the additional slides, I would need to change it to "Layer5Visited, Layer6Visited,..." so that each layer throughout the entire project has its own specific variable, is this correct?
Yup, the problem is using the same set of variables on multiple slides...
Variables maintain their value until a trigger changes it. So, as I said above, after the variables change to True on the first slide where they're used, they remain True. And that's why the next slide jumps after viewing just one layer. The conditions on the trigger are met before the user gets to that slide.
So, yes, you need different triggers for each slide. For easier programming (and troubleshooting), I suggest using a naming convention that indicates the slide and the layer. And keep the names as short as possible.
For example, the variables on the first slide could be s1_L1done, s1_L2done, s1_L3done, and s1_L4done. The variables on the second slide could be s2_L1done, s2_L2done, s2_L3done, and s2_L4done. And so on.