Hi, I have different narration on 4 layers and 1 shape linking to each. I want to allow learners to uncover each layer and make it visible but the issue I have is that users can click on another layer and if the narration hasn't finished on the previous layer, it overlaps. Hiding the slide layers in the settings is an option but I want the user to be able to see the text of each of layer as they click through, any ideas?
You can make use of the 'Pause Timeline' trigger to pause the timeline of the layers where you want to prevent the audio from playing.
There are other ways to approach this design inquiry, so if you're comfortable sharing your project file here, I'm sure other members of the community will have some suggestions to share.
Joe's solution is a great option. If you do not want them to select another layer until the audio is completed, you could use a Hotspot on the layers to cover those options up. You just need to have the hotspot leave the layer at some point so that they can select the next layer.
Thanks guys but I actually don't know how either option would work. I've attached the slide in question here.
Pausing the timeline on the layers doesn't stop me from selecting the shape. I'm not sure how the hotspot could be used to cover the other options up. For the interaction I want to show the details, i.e. the text as they click on each option but I don't want them to be able to click other options or play audio until the first one if finished.
I have reattached your story 2 times, each using the methods described above. One using the Pause option that Joe recommended, and the other using the hotspot mask.
Great, thanks for that Ron. I can see how the pause timeline works but I don't understand how the hotspot works. You just inserted a hotspot over the options for each layer without any triggers? How do they work?
Hotspots often have a trigger to do something. But in many cases, we use a hotspot just to cover something up. Similarly, you used a transparent rectangle on the base slide. That's pretty much the same concept. We like hotspots since they are more visible to the developer, but remain transparent to the end user.
8 Replies
Hi Philip,
Thanks for reaching out!
You can make use of the 'Pause Timeline' trigger to pause the timeline of the layers where you want to prevent the audio from playing.
There are other ways to approach this design inquiry, so if you're comfortable sharing your project file here, I'm sure other members of the community will have some suggestions to share.
Joe's solution is a great option. If you do not want them to select another layer until the audio is completed, you could use a Hotspot on the layers to cover those options up. You just need to have the hotspot leave the layer at some point so that they can select the next layer.
Thanks guys but I actually don't know how either option would work. I've attached the slide in question here.
Pausing the timeline on the layers doesn't stop me from selecting the shape. I'm not sure how the hotspot could be used to cover the other options up. For the interaction I want to show the details, i.e. the text as they click on each option but I don't want them to be able to click other options or play audio until the first one if finished.
Hello Philip,
I have reattached your story 2 times, each using the methods described above. One using the Pause option that Joe recommended, and the other using the hotspot mask.
Here is the pause option
I guess me posting to this question 2 times in a row with attachments - raised a red flag - looks like the Pause option did not make it through
This post was removed by the author
Great, thanks for that Ron. I can see how the pause timeline works but I don't understand how the hotspot works. You just inserted a hotspot over the options for each layer without any triggers? How do they work?
Hotspots often have a trigger to do something. But in many cases, we use a hotspot just to cover something up. Similarly, you used a transparent rectangle on the base slide. That's pretty much the same concept. We like hotspots since they are more visible to the developer, but remain transparent to the end user.