Inheritance diagram for qbehaviour_manualgraded:

Collaboration diagram for qbehaviour_manualgraded:

Public Member Functions
	adjust_display_options (question_display_options $options)
	process_action (question_attempt_pending_step $pendingstep)
	summarise_action (question_attempt_step $step)
	process_finish (question_attempt_pending_step $pendingstep)
Static Public Member Functions
static	get_unused_display_options ()
Data Fields
const	IS_ARCHETYPAL = true

Detailed Description

Question behaviour for questions that can only be graded manually.

The student enters their response during the attempt, and it is saved. Later, when the whole attempt is finished, the attempt goes into the NEEDS_GRADING state, and the teacher must grade it manually.

Copyright:: 2009 The Open University http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later

Definition at line 40 of file behaviour.php.

Member Function Documentation

adjust_display_options ( question_display_options $ options )

Make any changes to the display options before a question is rendered, so that it can be displayed in a way that is appropriate for the statue it is currently in. For example, by default, if the question is finished, we ensure that it is only ever displayed read-only.

Parameters:

question_display_options $options the options to adjust. Just change the properties of this object - objects are passed by referece.

Reimplemented from question_behaviour.

Definition at line 48 of file behaviour.php.

Here is the call graph for this function:

static get_unused_display_options ( ) [static]

'Override' this method if there are some display options that do not make sense 'during the attempt'.

Returns:: array of question_display_options field names, that are not relevant to this behaviour before a 'finish' action.

Reimplemented from question_behaviour.

Definition at line 43 of file behaviour.php.

process_action ( question_attempt_pending_step $ pendingstep )

The main entry point for processing an action.

All the various operations that can be performed on a question_attempt get channeled through this function, except for question_attempt::start() which goes to init_first_step(). question_attempt::finish() becomes an action with im vars finish => 1, and manual comment/grade becomes an action with im vars comment => comment text, and mark => ..., max_mark => ... if the question is graded.

This method should first determine whether the action is significant. For example, if no actual action is being performed, but instead the current responses are being saved, and there has been no change since the last set of responses that were saved, this the action is not significatn. In this case, this method should return question_attempt::DISCARD. Otherwise it should return question_attempt::KEEP.

If the action is significant, this method should also perform any necessary updates to $pendingstep. For example, it should call question_attempt_step::set_state() to set the state that results from this action, and if this is a grading action, it should call question_attempt_step::set_fraction().

This method can also call question_attempt_step::set_behaviour_var() to store additional infomation. There are two main uses for this. This can be used to store the result of any randomisation done. It is important to store the result of randomisation once, and then in future use the same outcome if the actions are ever replayed. This is how regrading works. The other use is to cache the result of expensive computations performed on the raw response data, so that subsequent display and review of the question does not have to repeat the same expensive computations.

Often this method is implemented as a dispatching method that examines the pending step to determine the kind of action being performed, and then calls a more specific method like process_save() or process_comment(). Look at some of the standard behaviours for examples.

Parameters:

question_attempt_pending_step $pendingstep a partially initialised step containing all the information about the action that is being peformed. This information can be accessed using question_attempt_step::get_behaviour_var().