Previous/Next Buttons delay when user goes back to quiz
Aug 27, 2014
I've embedded several Quizmaker knowledge checks with audio in my Presenter 13 compliance training course. The course is set up so that all slides run on auto, but the user can go back to review previous slides by pressing the previous button (I've removed the next buttons). When the user presses the previous button on a slide following a quiz, the course goes back to the quiz, and the previous and next buttons appear, but there's no response from pressing these buttons for about 15 seconds (sometimes shorter and other times longer). I've tried to work around this issue by setting the resume feature to Never so that the user would just have to retake the quiz, but the quiz always shows as complete. I've set the quiz to unlimited tries, both in the Quiz properties and in the slide view.
Is there any reason for the delay in response to the Previous and Next buttons? This is confusing my users, as they think the course is frozen and they need to exit and restart.
Thanks,
Anne
11 Replies
Hi A! I'm not sure that I have seen this behavior before. Would you be able to share your Articulate Package for us to have a look at? If you cannot share it here in the forums, you can share it here privately.
Hi Leslie - I've shared the Articulate package privately, as the information in the course is confidential.
Thank you! I have received your case (00418078) and will be taking a look.
Is there a solution to this problem? I converted my Storyline course into Storyline 2 and now the user can only proceed to the next slide after the timeline ends when they click Next. I am not sure how this is happening and it did it to two separate courses. I didn't add any new triggers to the Next button and it's still set to 'Jump to next slide when user clicks the next button'. There isn't a restriction to the timeline, yet that is what is happening on ALL of my slides! Please help!
Hi Martin! Do you have your navigation restricted by chance? Check out this article.
That's the one! Thanks for your help!
No problem Martin!
In Storyline 1 the menu restrictions did not affect the button triggers. Now in Storyline 2 the button triggers are affected when I select 'restrict' the menu. That seems really sloppy. I think developers should be able to choose to restrict the menu without it completely locking down the Next and Previous buttons... as it did in Storyline 1. I would hope Articulate would add a warning that restricting the menu also restricts the Next button... or better yet an option to not restrict the navigation buttons.
Hi Martin!
I can see why Articulate locked the navigation for the Next button with that setting, but it should really be up to the developer to turn that on. It's very confusing to have the menu setting lock the navigation setting without warning. Some of the slides have longer animations and just because a menu is locked, I'd still like users to be able to skip a slide. Right now it's kind of all or nothing; either fully locked down or not, which isn't the best option.
Thanks for your help though Leslie. Much appreciated.
This discussion is closed. You can start a new discussion or contact Articulate Support.