Articulate Presenter '13 Timing of Next button
Oct 19, 2016
I have been having a wide variety of technical problems with the HTML5 implementation and quiz corruptions so I decided to republish my course lessons with html5 turned off. During this process I turned on the seekbar in the template to address a different concern.
I turned on the Seekbar because of the constant complaints about clicking the next button not doing anything (which I have discussed with Articulate support previously).
The lack of indicator when a screen is done filling in with Studio 13 over Studio 9 is a huge deal for those of us that use restricted navigation.
I followed some suggestions to add a graphic at the bottom of the screen that is set in the animation pane to comes up last so that users will wait until they see that graphic before trying to click next. (A costly implementation!)
Even so there was still a problem. So I went again through all my lessons to make sure that the duration of the graphic is .01 and set to appear a few seconds after the last content on the screen appears.
Now that I turned on the seekbar the problem seems even worse than ever. With a duration for the animation set to .01 (smallest it can be), the last graphic shows up and there is a still a several second delay. After the graphic shows up indicating that everything should be done, done, done the seekbar continues to fill in for a second or two. Once the seekbar is done filling in I can click next.
The loss of the '09 feature where the next button was clearly locked or unlocked with Studio '13 was really a tragedy for people using restricted navigation. Without clear rules and explanations for how the timing is working I am at a loss. I don't use audio, just the powerpoint animation features. I have searched for any possible explanation and just can't find any information.
Can anyone provide insight into why a slide continues to remain locked up after all animations have appeared and their duration has run out? And any insight into why the seekbar timing is so different?