Hiding Layers When Seek Bar is Enabled

Jan 15, 2015

Hi everyone

I never use the seek bar on my courses, but a client has requested that I add one. 

It works fine except for slides that have layers on them. When a layer is revealed, if you use the seek bar to rewind back to the start of the slide, the layers stays revealed.

Is there any way to trigger the layer being hidden again if the learner resets the slide back to the start using the seek bar?



18 Replies
James McLuckie

Hi Emily

Thanks the input. I have tried this. Both the base layer and the layer in question are set to "reset to initial state" but the layer is still there even when the learner rewinds back to the start. 

The layer is revealed via a click trigger, not a timed trigger. Does that make a difference? 

Thanks again!

James McLuckie

Hi Emily

Thanks again for the reply. And sorry for the delay in getting back to you. 

File attached. It has two screens on it. One needs a button press to show the layer (press "Test the Seekbar"). The second has a trigger attached to the timeline. In both cases, the layer doesn't hide when I drag the seekbar back to the start. 

If you could take a look, that would be great. 

Many thanks in advance, Emily. :-)

Emily Ruby

Hello James,

Thank you for sharing the file. We do have an issue reported to the QA team about layers appearing when clicking and dragging within a seekbar. When any updates on this are available, I will post them here.

Using the rewind button at the end of the seekbar will reset the slide to its initial state.

Katie Riggio

Hi there, Charoma! Really sorry the layers appear when clicking on the seekbar in Storyline 360 as well.

I don't see a similar bug report for Storyline 360 and would love to take a closer look at your .story file to see if it matches Storyline 2's report. Mind sharing it in this discussion? You can also share it privately with me here. I'll be standing by!

Katie Riggio

Appreciate you sharing your project with us, Charoma! Seekbar timelines can get tricky after scrubbing the seekbar when layers are incorporated. 

This was a tough cookie! My team and I put our heads together and put all of the content from the layers on the base layer instead. With this approach, nothing will be out of sync with the voiceover when learners scrub the seekbar. Could this option work?

Since the file is private, I shared an updated version of it with you via email. Fingers crossed that solution works – we'll be standing by ☺️

Paul Colby

Another Storyline issue. Shocking! Why add the functionality to hide layers when using the seekbar? I think probably because that would be too easy and make too much sense.

Michael Lawrence's solution to this issue seems to work, although it doesn't seem to matter where I put the cue point.

I have developed two other solutions to this issue, neither of which is ideal.

1. My layers are usually triggered by a button. If that is the case, use the trigger shown in the attached file (HideLayers1.jpg) to hide the layer when you use the seekbar to go to an area of timeline where the button that showed the layer no longer appears.

2. If that doesn't work, you can add an empty layer, let's call it "HideAll" . You can then add an invisible rectangle named "HideAllPopupsForSeekbar" onto your timeline and extend it according to where you want the layers to hide when using the seekbar. Then add the trigger shown in the attached HideLayers.jpg


Mark Lentz

With narrated presentations, I like to throw up the key words as they are spoken, and having them on separate layers works better production-wise compared to trying to cram them into the base layer.  But I want the users to be able to use the seekbar without issues.

For me, an version of Michael Lawrence's solution:  a cue point on the base timeline hiding all layers at the point the last one disappears, and a second doing the same thing at the very beginning of the time line.  Then users can scrub away with no problem... Using the "Group Triggers" feature makes this solution appear neater.

I wish the HTML5 version could instead just "parse" the slide's entire timeline before it decides what should layers should be displayed at any point, but... as long as we can get it to work somehow in the meantime!