Using the seekbar is making hidden objects on screen appear -- and I don't want them to.

Hi Brooke, 

I think we're going to need a little more information or ideally a copy of the slide in question.

Thanks! I'll upload the file to support.

Hi Brooke,

Great call to reach out to our support team! It looks like Bang was able to replicate the issue you were running into where dragging the seek bar resets the state of an object.

I'm sorry you're running into this bug, but we'll be sure to reach out to you in your case, as well as in this discussion when we have any progress to share.

Thanks Ren!

Folks, I've discovered a related issue, so I mocked up a couple of slides. I have two shapes, a rectangle and a triangle, appear on the slide at the 1 second and 2 second mark (approximately) The user is prompted to click the shapes to change them to a hidden state. I have a layer that pops up when the state of Triangle1 and Rectangle1 are hidden.

When the slide starts, or when you go back to the slide from the menu or by using the Previous button on the next (blank) slide, it works normally. However, if you select the REPLAY button on the seekbar, OR if you drag the seekbar to a point before the first shape appears, it will open the layer that should only be triggered by the hidden states.

The bug seems to be that when an object is placed somewhere else on the timeline other than the 0-second mark, its state seems to be 'hidden' (according to the seekbar) when the seekbar gets interacted with and gets moved to a point in time before the object appears. This is definitely a bug if one is relying on hidden states as a trigger.

Thanks for sharing your findings, David. I appreciate the description of the issue along with the .story file to demonstrate.

I'm seeing the same issue you are reporting, but I am unable to nail down the culprit. 

I've opened a support case on your behalf so that one of our support engineers can take a look and dig in a bit further. You should be hearing from someone soon.

Thanks, Leslie. Again, it really seems like an object that is put at a location other than the very start of the timeline is in a kind of 'hidden' state that becomes visible when the object's own timeline starts. Slide triggers for hidden state don't seem to have problems distinguishing this EXCEPT when the seek bar is enabled and you use it to move backwards in the timeline to a point before the object's timeline starts. (Not that it really helps understand WHY, but at least it's a predictable behaviour.)

I appreciate the follow up!

Agreed and I appreciate the additional info. I've passed this on to Cleo who is currently taking a look 😊 

Any movement on this issue? I have a project right now that has this same problem. For now I have locked the seekbar but that is not an acceptable user experience. Any thoughts? Thanks.

Hi William,

The issue reported here is when dragging the seek bar, the state of an object re-sets. This is still an open issue with our team, so I do not have any additional information to provide at this time.

I wanted to share some information on how we define bugs and how we tackle them when they occur.

I was afraid you would say that. This issue also occurs if you use the Play/Pause button in the player. 

In the interim, I found a workaround.

1. I added a trigger to pause the timeline of the slide as soon as the slide loads.
2. I placed a "play media" icon over the video with a duration of .25 sec.
3. I added a trigger to the icon that resumed the timeline when clicked.
4. Done

No problems with dragging seekbar or using the play/pause button in the player.

It would be awesome to see a solution from Articulate but I understand that there are more pressing issues. Thanks so much for your reply Leslie. 

Hey William!

I appreciate you sharing the additional details and workaround. The behavior reported here only happens when dragging the seekbar. I tested this on my end, and I didn't see the object re-set when I click the player's Play/Pause buttons. Here's my test.

From here, I'd recommend connecting with one of our support engineers to take a look at your file to investigate what could be causing that!

I did the same it worked. This one is just a workaround but beneficial on temp basis.

I'm glad that William's solution was able to help you as well, Vinnie. I appreciate you chiming in to share and welcome to E-Learning Heroes. 😊

Hello, I'm wondering if this issue has been fixed? I have a video triggered to play by a button within a text box that is on top of the video. When the user clicks play, the text box and button change state to hidden. However, if the user clicks the seekbar both reappear on top of the video. There are workarounds, like pausing the timeline and only having the text and button on the timeline for a second or animating them out, but it would be much better if I didn't have to do that.
Thanks for any updates!

Hi, Stephen.

We don't have any updates to share for this bug fix yet, but I'll be sure to come back when we have news, as this discussion is linked to the report.

Hi Stephen. One of the things I've done is to place the button and text box on a different layer and simply launch that layer when the slide starts. Once the button is selected, trigger the Play Media and then the Hide Layer triggers and the button won't come back unless you specifically trigger it to.

Hello everyone!

I have great news to share! We are no longer seeing this bug where dragging the seek bar resets the state of an object when using our latest version of Storyline 360 (Build 3.72.29699.0).

Please let us know if you’re still noticing the issue, and we’ll be happy to continue troubleshooting with you in a support case.

This is great news.

I still notice this issue when I set the state of something to hidden on a click (in this case it's a button). If I use the seekbar and pull it to the beginning of the timeline, then it resets the button back to its original normal state. 

Hi Adam!

Sorry to hear you've run into this issue!

Testing the behavior on my end (32 & 64-bit Storyline 360 version 3.82.31354.0 via Windows Parallels on a Mac M1) I too was able to replicate the same issue.

I've opened a support case on your behalf and shared your feedback with our support engineers. You're in great hands working with them and they should be getting in touch with you shortly!

Thank you for bringing this to our attention. Sorry if it has been slowing you down!