Help with Pausing Timeline Issue

Feb 20, 2020

Anji Heath
By Anji Heath

Hello,

I have a project that was created in SL 2. I updated it to 360 and my colleague edited it using SL 3. Currently, when a user clicks a link, like slide notes or a link to a reference, the timeline isn't pausing automatically like it normally would. Could a support person provide any insight to what the problem is? I could have a trigger to set the timeline to pause; however, our learners aren't used to having to click the play button when they return to the activity so that is not my first choice here. I'm just confused why this would seem to happen randomly. 

Thanks in advance. I've attached the SL file.

3 Replies
Anji Heath
4 years ago02/20/20 at 4:53 pm (UTC)

OK...I did some more checking so I wanted to provide an update to this, mainly for the tech support folks. If you look at this module that I published several months ago, you'll see that when you play the activity and click to access the documents in the Resources section, the module will pause the audio on the timeline, then resume once the user has closed the browser window. https://360.articulate.com/review/content/2b873d11-8671-4ccd-9496-1acf59f5c157/review 

Now compare that to the one that was published this morning: https://360.articulate.com/review/content/80a58c48-4b95-4d83-890c-38fb2b2acbdb/review Note that when you click on the documents in the Resources section, the audio doesn't pause. To make it extra special, the timeline appears to run long then. You can see that once you click off it, the timing of the bullets and ending of the slide is all off after you close the open browser window. This can be double-checked be referring to the actual SL file where you can see the timing for the end of the slide and bullets is as it should be. I definitely think there is a bug in one of the recent updates that is causing this issue.

Leslie McKerchie
4 years ago02/21/20 at 7:08 pm (UTC)

Thanks for contacting our support team as well, Anji

I see that Phil was able to work directly with you and has shared the details for our team to further investigate.

This conversation is linked to the report so that we can share updates with you here when we can.

In the meantime, installing Update 35 should alleviate the issue you're seeing if needed.

This discussion is closed. You can start a new discussion or contact Articulate Support.