Forum Discussion

AnthonyGill-e99's avatar
AnthonyGill-e99
Community Member
2 years ago

Problem with trigger sequence for next button

I am using SL3. I Have created a slide that requires the 7 button presses before the Next button state will change to Normal. I want them to be able to press them in any sequence. I accomplished this by creating 2 countering triggers (see 1.3) What I do not understand is what is wrong with the other 2 (1.1 and 1.2). I have to press the buttons in the sequence I describe on the slide or the Next button will not change state. This is odd considering I am using the AND condition. 

  • Hello Anthony, 

    Thanks for reaching out! 

    I recreated your triggers so that your learners can now view the icons in any order to trigger the availability of the Next button. 

    There are many ways to approach your design requirement, but I implemented a design that utilizes True/False variables to track the completion of the 7 buttons as my personal preference.

    I created two variables for testing, set_1 and set_2. Set 1 will be assigned a True value when the three buttons on the main layer are viewed, and Set 2 will change when the 4 icons on the one of the layers is similarly viewed by the learner. 

    Attached is a copy of your edited project file so you can check out the changes that I made to your slides. 

    Let me know if you have any questions!

  • When I compare this to the 1.3 slide that I sent it is the same thing. The both triggers are needed for it to work properly. I am curious as to why this is. It would seem logical that one of the triggers would work regardless of the sequence. I am just looking for understanding as to why just one of them would not work. Does it have something to do with the order?

  • 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.

     

     

  • Can you resend me this sample in SL 3 version. I do not have 360 due to our policy. I am not able to open it. Or send me a screen shot of the trigger.

  • I can't right now, but here is what I did to make it work.

    Change the Ancillary layer to Resume changed state in layer properties.

    Delete this trigger:

    Apple, Pear, and Turkey all get a new trigger, so the change is not dependent on the change of the 1_5AllVisited variable. Those triggers look like this:

     

    By the way, I would not use a shape and a text box, and I would rather be poked in the eye with a sharp stick than to use a group. It causes too much baggage and clutter. Create the shape, click on it, and type. It makes the text part of the shape, and you can change it any way you can change text in a text box.

    On the ancillary layer, each of the four icons gets this trigger: