TaskManager

The TaskManager is a special node that runs a storyboard made up of several tasks nodes. The storyboard is like a workflow.

• Define a task hierarchy to group tasks together logically.

• During storyboard playing, many tasks can simultaneously be in running state. This gives the storyboard writer great flexibility.

• The end tag must be used to terminate a task with success or with failure.

Platform support

This node is supported on XR-Windows platform only.

Task states

Each task can exist in four states.

Changing status of a task

There are two ways to set a task from waiting to running. Both ways can be used to start one or more tasks.

• From another task activation using startTasks task parameter.

• From another task end using startTasks end parameter.

Scores

Each task can be associated one or more score clauses. If the node changes its state to Success, the score is added to Task Manager score. Scoring has a hierarchical handling so for each task we are able to know its maximum possible score (summing its and its children scores) and current score.

There are two kinds of scores: shot and time.

A task can have 0,1, or more score clauses.

There should alway be only one TaskManager running at a time inside an application.

Task management and multi-player

To enable more than a one person (players or instructor) to participate in the same scenario, the task management must be configured and managed in the proper way. You must locate and execute the Task management code (task completion, score calculation) in a unique place. This is generally the server of the message bus network. Each TaskManager must have mode set to master in a unique application node and to slave in all the others.

To enable master update, the slave parameter taskStates must be shared. Slave update includes only task state and not all the other information.

Code example

This is a code example for the TaskManager node.

<taskmanager name="tm_0" >

<task name="mission" startTasks="t1">

<task name="t1" title="Power On" description="" startTasks="t1_1">

<task name="t1_1" title="Turn Insulator Power On" description="Turn KSHEON to On" >

<end condition="@KSHEON.value@==1" />

<score value="5" type="shot"/>

</task>

<end condition="@tm_0.t1_1_state@==success" startTasks="t2"/>

<score value="50" type="time" timeRange="20 200"/>

</task>

</task>

</taskmanager>

TaskManager fields

These are the fields for TaskManager node. Only the node-specific fields are indicated, not fields obtained by inheritance.

Field inheritance: NodeBase > TaskManager

Task Attributes

The parameters of the task can be accessed with the syntax:

taskManagerName.taskName_taskField

For example: tm_0.t1_1_state

End attributes

Nodes of this clause are conditional endings for a task, so there is no way to access their parameters from outside. They have no name parameter.

Score attributes

The score nodes are attributes of a task, so their parameters are not accessible from outside. They have no name parameter.