Hello,
It is well known that including the Back and/or Next buttons in Captivate quiz questions presents real problems. I have come up with what I think to be a solution. It should allow one to include both Back and Next buttons, if one wants to do this. It involves doing the following:
- With Question 1, do not include a Back button. (This is so that the quiz-taker cannot get out of the quiz scope in the forward direction.)
- Create this advanced action: If cpQuizInfoTotalUnansweredQuestions = 0, then Go To The Next Slide (i.e. the results slide); Else Continue.
- Insert a slide after the final question (and before the results slide). On this slide, include the following:
- A message to this effect: ‘You have not answered all of the questions. Please go back and complete all of them.’
- A button labeled ‘Return to Questions’ (on success: Jump to slide with Question 1). But include no other buttons. That is, if the quiz-takers lands up on this slide, he or she has only this option.
- On Enter (i.e. on entering the slide being described here), Execute Advanced Action = the advanced action described in Item 2 above.
- Now for something odd. Before the slide described in Item 3, insert a slide with a Text Caption with variable $$cpQuizInfoTotalUnansweredQuestions$$. Keep the slide as brief as possible (something like 0.5 sec.) and make the text of the Text Caption invisible. And why all this? Because I found that, without it, problems arose quite regularly. If one or more questions were not answered, the quiz-taker would come, as expected, to the slide described in Item 3 above. The quiz-taker would then go back to complete the unanswered questions. But then—sometimes—the Item 3 slide would still appear, even though all the questions were answered! The quiz-taker would return once again to the questions (since this is the only option available), only to find that now none of the questions were answered! And at this point, there was no escape: the Item 3 slide would always appear no matter what one did. Why should inserting the additional slide described in the present item solve the problem? I don’t know. All I can say is that (1) without it, the problem arises often (though not always), and (2) with it, the problem hasn’t occurred yet, even though I’ve done lots of testing.
Final note. It will be clear that this solution is meant to be used together with the option Allow Backward Movement. Will the solution work with Branch Aware? I don’t know yet. Will it work with Question Pools? Again, I don’t know yet. I’ve only done a bit of testing in both cases. The results thus far indicate that at least one of these options presents real problems. Both might.
I’m still testing this solution (or what I hope is a solution). If anyone else wants to try it, I’d be interested in hearing how it goes.
Best regards,
Marvin DuBois
