7 Replies
Alexandros Anoyatis

Hi Elena,

In your case, you don't really need a layer to display your 'slide 2' elements (if it is absolutely necessary, then you will have to go about it a different way then the one in my attachment).

I repositioned the slide 2 elements and modified your existing triggers to reflect this change. I also added an unconditional variable reset when timeline starts to keep things simple and error free between any user 'back-and-forths'...

The logic in scene 1 works, however I like the way you make use of the triggers in slide 2 better (no listeners involved).

Hope this helps,
Alex

Alexandros Anoyatis

No, the real issue was that you positioned (and referred to) slide layer elements in your base layer triggers without actually getting to the slide layer itself.

As for the reset trigger, what you did works most of the time, but not always. Here's a scenario :

Learner goes through Slide 1 and clicks 'Next' which takes him to slide 2. Then the learner clicks/reveals only 2 elements (value of ButtonCount is 2) and then -whatever the reason- clicks on the 'Previous' button. He would then go back to Slide one, only the button count will immediately become 3 once Next is pressed again - which will kind of break your regular flow - especially if you are dealing with more than 2 slides in your final story file...

Unconditionally resetting the variable value of ButtonCount to 0 every time you revisit a slide that functions this way, would save you from these unfortunate situations...

Hope this helps,
Alex