Triggers Tied to Multiple Layers

Jul 19, 2012

I'm wondering if you can set a single trigger to have a layers appear sequentially.  For example, the first time you click a trigger, layer one appears.  The second time you click a trigger, layer two appears and so forth.  Since I am basing the triggers on a background picture of a tool, I can't put multiple triggers over the same area.  The procedure I am showing requires the user to click the same button three times throughout the slide.  Just want to know if it is possible, or will I have to break the procedure down into seperate action slides.  Thanks

5 Replies
Rebecca Fleisch Cordeiro

Hi David,

First, I don't know how to set a single trigger in the way you describe, so need to get that out there!

You say the Learner must click the same button 3 times throughout the slide, so I'm not sure if what I did is different, but I thought I'd throw it out there.

I created a shape on each successive layer, in the same spot where the original "tool" was. So, the Learners must click on the tool at each layer, but only 1 click each time. So

  • On the base layer, they click the tool to get to Layer 1
  • On layer 1, they click the "overlaid tool" to get to Layer 2
  • On layer 2, they click the new "overlaid tool" to get to Layer 3

So, wondering if you could do the same thing with a screenshot of the tool from the base layer overlaid on each layer and set the triggers from there.

Jeanette Brooks

Hi David! Great question, and for sure — you can do that. Attached is an example. I used a simple number variable to count how many times the learner clicks the button, and used that as the basis of my triggers, so that Storyline knows which layer to reveal. Once the final layer is revealed, I also included a reset button which allows the learner to do the whole thing over again if they want. 

In this example, I chose to keep all layers visible throughout the slide, but if you want each layer to display independently of the others, you could do that by adjusting the slide properties.

This discussion is closed. You can start a new discussion or contact Articulate Support.