The Back button for the QuestionWidget.

See also

The Clear button for the QuestionWidget.

See also

Determines if Captivate sees the question as complete (true) or incomplete (false). If Captivate picks up that the question is incomplete, it will not accept the question as correct or incorrect, and will show the 'You must answer the question' callout.

The audience is then given another opportunity to answer the question.

It is best to set the value of this property in the submit() Template Method, or during the QuestionWidgetEvent.SUBMIT event.

The default value is true.

See also

Determines if Captivate marks the question as correct (true) or incorrect (false). Captivate will first look to see if isCompleteAnswer equals true. If so, then it will check isCorrectAnswer. If not, then Captivate will skip over isCorrectAnswer and give the audience another chance to answer the question.

When isCorrectAnswer is returned as true, Captivate marks the question as correct, and displays the success caption.

When isCorrectAnswer is returned as false, Captivate marks the question as incorrect, and displays the failure caption.

Depending on how the Captivate Author has set up the question, the audience may be allowed another chance at answering the question after submitting a wrong answer.

Once the question has been answered correctly, or the last failure level reached, the QuestionWidgetEvent.DISABLE_ANSWERS event and disableAnswers() Template Method are fired, and the movie moves on to the next question.

The default value is false.

See also

Holds a string that is sent to the Learning Management System (LMS) when the question is submitted. The LMS will return the string to the widget if the user revisits the lesson later to pick up where they left off.

When the user opens up the course again, the widget will have to reload, but will have no memory of how it was set up when the user left it. The widget developer must include enough information in the questionState string to enable the Question Widget to be configured exactly as it appeared when it was submitted by the user. Additionally, the developer must code the widget so when it receives this information, when the QuestionWidgetEvent.QUESTION_STATE_SET is dispatched, it will know what to do with it.

See also

        
        var xml:XML = new XML(<questionState/>);
        xml.textField = "Hello";
        xml.selectedAnswer = "Answer1";
        questionState = xml;
        
          addEventListener(QuestionWidgetEvent.QUESTION_STATE_SET, questionStateReturn);
        
          function questionStateReturn (event:QuestionWidgetEvent):void {
           var questionStateXML:XML = new XML(questionState); // Turns the string into XML data
           onstage_txt.text = questionStateXML.textField; // The on stage text field will read the value of the 'textField' property we wrote on the XML object.
        }
        
        

The container of the Question Text field for the QuestionWidget.

See also

The container of the Question Title text field for the QuestionWidget.

See also

The Quiz Reporter object that is associated with this quiz question. For more information see the QuizReporterProxy class.

See also

The score that will be reported to the quiz (assuming the question reports as correct).

This can be altered to give a partial score which is different to the one the Captivate Author set up under the Quiz Properties panel > General Settings > Points.

The Skip button for the QuestionWidget.

See also

The Submit button for the QuestionWidget.

See also

Creates a new instance of the QuestionWidget class.

Adds an answer to the Answer list.

The Answer List is requested by Captivate after the question has been submitted by the user. Make sure you set up all your answers before or during the QuestionWidgetEvent.SUBMIT event, or submit() Template Method.

See the Answer class for more information on Answers.

Parameters

See also

Clears the Answer List of all Answers.

See also

A Template Method that is called when this question's 'Clear' button is pressed. Depending on what your Question Widget does, clearing it may mean any number of things.

In overriding this Template Method, you should code your widget so that it restores the question to its initial state. For example: In a drag and drop widget, you would move all draggable items back to their starting positions.

If you do not call super.resetAnswer() at the end of this function, the QuestionWidgetEvent.RESET_ANSWER Event will not be dispatched.

See also

A Template Method that is called when the user reviews the quiz and reaches this Question Widget. It is called once for each Answer in the Answer List. This method is called regardless of whether the question was answered correctly or incorrectly.

You can access the properties of the Answer through the passed in parameters.

        
        override public function resetAnswer(answerID:String, chosenAnswer:String, correctAnswer:String):void {
           trace(answerID);
           trace(correctAnswer);
           trace(chosenAnswer);
        }
        
        

You need to enter an answerID when you create an Answer object, because otherwise, there would be no way to identify the current answer from any others that were in the Answer List.

Parameters

See also

A Template Method that is called when the question's interactivity should be turned off.

This method is called when the question has been answered. It's called again when the Question Widget is being reviewed.

disableAnswers has a matching method of enableAnswers, which is called when the interactivity for the widget should be turned on. Ideally, the actions of both these methods should cancel each other out, meaning Captivate could enable or disable the question as many times as it needs, and still result in no error.

If you do not call super.disableAnswers() at the end of this function, the QuestionWidgetEvent.ENABLE_ANSWERS Event will not be dispatched.

See also

A Template Method that is called when the question's interactivity should be turned on.

This method is usually called right when the question appears on screen. It is considered better practice in the case of Question Widgets to override and put your runtime code in the enableAnswers() method instead of enterRuntime().

enableAnswers has a matching method of disableAnswers, which is called when the interactivity for the widget should be turned off. Ideally, the actions of both these methods should cancel each other out, meaning Captivate could enable or disable the question as many times as it needs, and still result in no error.

If you do not call super.enableAnswers() at the end of the method, then the QuestionWidgetEvent.ENABLE_ANSWERS Event will not be dispatched.

See also

A Template Method called when the LMS returns the questionState string. The questionState string can be read via the passed in questionState property...

         override public function setQuestionState(questionState:String):void {
            onStage_txt.text = questionState;
         }
         

         override public function setQuestionState(questionState:String):void {
            onStage_txt.text = this.questionState;
         }
         

Because, as you see, there is a whole lotta difference there.

Parameters

See also

A Template Method that is called when the 'Submit' button is pressed. This method is called just before the question's results are sent off to Captivate. In overriding to this Template Method, you should check whether the answer submitted by your widget is complete and correct, then set the isCompleteAnswer and isCorrectAnswer properties accordingly.

See also

Tells Captivate to start the Question Widget's submit process.

This is useful in the case that you have created a question where clicking the Submit button at the end would not make sense. For example, if you had a widget where you had to win a car race, it wouldn't make sense to click the submit button after the car has crossed the finish line. In that situation, you would call this method at the end of the race. The submit() template method and WidgetEvent.SUBMIT event will both still be fired as if the user had clicked the submit button.

In responding to this event, you should code your widget so that it restores the question to its initial state. For example: In a drag and drop widget, you would move all draggable items back to their starting positions.

See also

You can access the properties of the Answer object through the QuestionWidgetEvent object that is passed into the function.

        
        addEventListener(QuestionWidgetEvent.COMPARE_ANSWERS, onCompareAnswer);
        
           function onCompareAnswer (event:QuestionWidgetEvent):void {
           trace(event.answerID);
           trace(event.correctAnswer);
           trace(event.chosenAnswer);
        }
        
        

You need to enter an answerID when you create an Answer object, because otherwise, there would be no way to identify the current answer from any others that were in the Answer List.

See also

This event is dispatched after the question has been answered. It's dispatched again when the Question Widget is being reviewed.

DISABLE_ANSWERS has a matching event of ENABLE_ANSWERS, which is dispatched when the interactivity for the widget should be turned on. Ideally, these events should cancel each other out, meaning that Captivate could enable or disable the question as many times as it needs, and still result in no error.

See also

This event usually fires at the point when the question appears on screen. It is considered better practice in the case of Question Widgets to use ENABLE_ANSWERS than ENTER_RUNTIME. The reason for this recomendation is that ENABLE_ANSWERS has a matching event of DISABLE_ANSWERS, which is dispatched when the interactivity for the widget should be turned off. Ideally, these events should cancel each other out, meaning that Captivate could enable or disable the question as many times as it needs, and still result in no error.

See also

This event can be listened to by Static and Interactive Widgets, not just Question Widgets.

         public function ConstructorFunction ()
         {
             addEventListener(QuestionWidgetEvent.SET_QUESTION, onSetQuestionState);
         }
         
         override public function onSetQuestionState(event:QuestionWidget):void {
            onStage_txt.text = event.questionState;
         }
         

         ublic function ConstructorFunction ()
         {
             addEventListener(QuestionWidgetEvent.SET_QUESTION, onSetQuestionState);
         }
         
         override public function onSetQuestionState(event:QuestionWidget):void {
            onStage_txt.text = questionState;
         }
         

See also

See also