I have a slide that shows a layer when the base layer timeline reaches a certain point.
When previewing, after the layer is shown, if the user drags or clicks the seekbar at an earlier point in the timeline, the layer still shows. Is there a way to hide the layer when this is done?
Any time the seekbar is dragged, the layer will show. SL has never learned to calculate what should be happening at any given point in the timeline. It's like a little kid that can add six and three only by starting at three and counting six more fingers.
You'd think they could set up a variable for when the seekbar position is less than its maximum position. This way you can set triggers to work off that seekbar variable.
This particular slide has 2 layers. One shows when cue point 1 is reached, and the other layer shows when cue point 2 is reached. The base layer is always shown.
I created a variable, counter, with a default value of zero.
The base layer has this trigger: Set counter equal to 0.00 when timeline starts.
The layer that shows when cue point 1 is reached has these 2 triggers, in this order:
Add 1.00 to counter when timeline starts
Jump to (name of this slide) when timeline starts if counter greater than 1.00
The layer that shows when cue point 2 is reached has these 2 triggers, in this order:
Add 1.00 to counter when timeline starts
Jump to (name of this slide) when timeline starts if counter greater than 2.00
I tested this when the seekbar naturally passes those cue points and when clicked past those cue points and it worked fine.
Problem solved. I used other techniques for replay workarounds on other slides with layers because the triggering of those layers was based on user interaction, not the timeline, as is the case with this slide.
Hope this helps those of you who need this kind of workaround.
Thanks John for sharing that workaround. As for the additional variable it's a neat idea, and I can understand how that would make life easier. I think it would be worth telling our product team about it here!
Thanks for checking back! This isn't a feature that we currently have in Storyline 360. Right now, dragging the seek bar earlier won't remove the layer since it's triggered to show at a certain point. To achieve this, you would still need to use the workaround.
would like to bump this one again. There is a similar thread a few years older as well. Would be a huge time saver and help with large production teams working from templates (I need to rely on your excellent simplified triggers with the team vice work arounds, although this one is very clever thank you John)
Thanks for sharing your need for a way to hide layers when dragging the seekbar back.
Although this currently isn't an option in Storyline, I documented your thoughts with the right folks. If there's any forward movement, we'll let you know!
In the meantime, another approach could be to add a cue point at the beginning of the base layer's timeline. Then, add a trigger that hides the layer when the timeline reaches that cue point.
11 Replies
Any time the seekbar is dragged, the layer will show. SL has never learned to calculate what should be happening at any given point in the timeline. It's like a little kid that can add six and three only by starting at three and counting six more fingers.
Thank you, Walt.
You'd think they could set up a variable for when the seekbar position is less than its maximum position. This way you can set triggers to work off that seekbar variable.
I came up with a workaround that works.
This particular slide has 2 layers. One shows when cue point 1 is reached, and the other layer shows when cue point 2 is reached. The base layer is always shown.
I created a variable, counter, with a default value of zero.
The base layer has this trigger: Set counter equal to 0.00 when timeline starts.
The layer that shows when cue point 1 is reached has these 2 triggers, in this order:
Add 1.00 to counter when timeline starts
Jump to (name of this slide) when timeline starts if counter greater than 1.00
The layer that shows when cue point 2 is reached has these 2 triggers, in this order:
Add 1.00 to counter when timeline starts
Jump to (name of this slide) when timeline starts if counter greater than 2.00
I tested this when the seekbar naturally passes those cue points and when clicked past those cue points and it worked fine.
Problem solved. I used other techniques for replay workarounds on other slides with layers because the triggering of those layers was based on user interaction, not the timeline, as is the case with this slide.
Hope this helps those of you who need this kind of workaround.
Thank you,
John
Thanks John for sharing that workaround. As for the additional variable it's a neat idea, and I can understand how that would make life easier. I think it would be worth telling our product team about it here!
Has this been fixed or do we still need to use that workaround? :)
Hello Borgthor!
Thanks for checking back! This isn't a feature that we currently have in Storyline 360. Right now, dragging the seek bar earlier won't remove the layer since it's triggered to show at a certain point. To achieve this, you would still need to use the workaround.
would like to bump this one again. There is a similar thread a few years older as well. Would be a huge time saver and help with large production teams working from templates (I need to rely on your excellent simplified triggers with the team vice work arounds, although this one is very clever thank you John)
Good morning, Steve!
Thanks for sharing your need for a way to hide layers when dragging the seekbar back.
Although this currently isn't an option in Storyline, I documented your thoughts with the right folks. If there's any forward movement, we'll let you know!
In the meantime, another approach could be to add a cue point at the beginning of the base layer's timeline. Then, add a trigger that hides the layer when the timeline reaches that cue point.
Thanks!
How would I then show the layer at the end of the timeline?
I did open a ticket with a sample course, also attached here
Hi Steve,
I appreciate you sharing a feature request. I've linked it to the report that Katie mentioned above.
I reached out to Katie so that I could share her suggestion in a file for you to take a look and what we came up with is attached.
Fantastic support, thank you! This is a perfect solution that I can trust to function in the LMS. Thank you so much, have a great weekend
This discussion is closed. You can start a new discussion or contact Articulate Support.