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.