Forum Discussion
Problem with trigger sequence for next button
I only looked at slide 1.1, but there is a reason why it won't work, and actually it does have something to do with the order.
There are other ways to get it to work. In fact, the only way it doesn't work is if you click both Pear and Turkey before you visit the four icons on Apple. In other words, it only works if Pear or Turkey is the last layer visited. Any other way works.
Generally, this trigger will work, but only when all four icons are clicked in sequence. If you visit fewer than all of them, then visit Pear or Turkey, then return to Apple, none of them will be visited. (It needs to do this to fulfill your requirement of any sequence.) That is because the Ancillary layer is set to "Reset to initial state on Revisit". Change it to "Resume saved state, and it will probably work.
What is a bigger problem is the combination of these two triggers:
1_5AllVisited is changed only when the third of the three rectangles is clicked. So if you visit Turkey and Pear first, it changes when you click Apple, but never changes again. At that point 1_5AllBTN is false, so NEXT does not change. When 1_5AllBTN does change, it is too late, because 1_5AllVisited will not change again.
This trigger then, will not be true unless all four icons are clicked before the third rectangle is clicked.
To truly be able to click all seven buttons in any order, each button needs to have a trigger that will change NEXT if it is the last button clicked. Change Ancillary to Resume changed state, and give each button a trigger, so the change is not dependent on the change of the 1_5AllVisited variable, and I think it will work the way you describe.
In the attached sample, see the new triggers for the three rectangles on slide 1.1, and the four btns on the Ancillary layer.