Showing Layers When Timeline Ends AND user clicks
Jun 08, 2022
I'm trying to define when a participant can click on a new layer (for example a timeline or process diagram). All templates have triggers set where 'show layer when user clicks 'rectangle 1'. However I want to be sure the participant listens to all audio on the base layer first before they can click. Yet if i choose 'timeline ends on slide' the first layer will appear automatically. This is ok for the 1st layer, but I need to do this on a slide that has multiple layers.
I've attached a screen shot of what I've tried.
Any suggestions?
Thanks,
Morgan
16 Replies
Hey Morgan. Ok, so from your screenshot, I see a trigger set to show the Specify Value layer when the timeline ends...but only if the Specify Value marker/button is in the Selected state. Is that necessary? I'll have follow up questions based on your response...
Hi Daniel,
The reason I did that is to prevent the layer automatically appearing after the base layer is complete however I'm all ears to other suggestions!
Gotcha... Ok, so you want the layer to appear once the learner has heard the entirety of the audio on the base layer, correct? If so, a trigger that reads "Show layer Specify Value when Audio 1 completes" should do the trick, right? Something like this:
https://360.articulate.com/review/content/e4d5498c-16d8-4827-829c-67c223433ca9/review
Is that not what you're going for?
Hi Daniel,
Thanks, this is ok for the 1st layer however how do I format the 2nd, 3rd, 4th & 5th layers?? I would like the learner to go in sequential order throughout the process.
Thanks,
Morgan
Great! And awesome, that was going to be one of my follow up questions: Whether you want learners to view Specify Value (SV) first, then IVS next, and so on... That makes things easier.
One way you could go about this is to establish up front, visually, that items 2-5 are inaccessible until you go through the steps in order, and then setting up triggers that limit when certain objects become Normal again on the layer level. I've updated the link again to show how this would work.
Also attaching a working SL file.
I was kind of thinking this but I never would have been able to explain it as well as Daniel did!
Too kind, Kandice. Too kind! 😄
Daniel, thanks for sharing your solution!
Morgan, welcome to the E-Learning Heroes community! 🙂 Also, it looks like your email signature came through when you replied via email. If you want to remove any personal info you don't want to share with the community, just log into the community and click Edit below your comment.
Thanks Sarah!
This makes sense, thanks Daniel.
The only issue I'm having is that I have the ovals to appear using 'cues'. However yours uses 'animations'. Are cues not an option for triggers?
Thanks,
Morgan
This post was removed by the author
Ah! Misunderstood what you were asking... Yes, cues are totally an option! Just swap out "when animation completes" for "when timeline reaches cue point [1, 2, 3...]" :)
This post was removed by the author
Woohooo! It worked ;) Thank you!
Hi again,
I got my first slide to work but now for some reason my 2nd one with a similar format isn't. The only different I can tell is that the 'base layer is hidden' on slide 1 vs. slide 2. It's slide 2 that I want to act like slide 1.
Any help would be appreciated!!
Hi Morgan! Can you share a bit more about what you're looking to do for slide 2? And what's not working? I want to make sure I understand so I can point you in the right direction.
What I would do is use states of an object or a variable.
Set up your triggers like this
Change state of [object1] to [StandBy] when media [audio1] completes
Show layer/jump [layer1/slide1] when user click [objet1]
If [object1] = [StandyBy]
You might have that state be slightly different so the user knows that it is actionable. This could be done by having disabled be the default button state and then change to normal.
One thing that leapt out to me as I tried it. I had no idea why the buttons weren't working. As a user we expect, rightly so, that when there's a button something is going to happen when we push it.
The disabled states look like they should work. It is very annoying when they don't but you think they should.