Difference between revisions of "Undocumented Custom Task"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
. . . | . . . | ||
where you provide name of the task and its parameters as required by the task. The name and parameters are all case sensitive (in contrast to known | where you provide name of the task and its parameters as required by the task. The name and parameters are all case sensitive (in contrast to known tasks, which may be tolerant of different cases). In <tt>XML</tt> files, an unknown task is scheduled using a <tt>Schedule</tt> element, which must be within the single <tt><CustomTasks></tt> block: | ||
<Schedule name='newTask'> | <Schedule name='newTask'> | ||
| Line 13: | Line 13: | ||
</Schedule> | </Schedule> | ||
The use of unknown custom tasks allows you to | The use of unknown custom tasks allows you to implement user-written custom tasks. For more details on writing custom tasks, see the help on [[Writing a Custom Task|developing a custom task]]. | ||
Latest revision as of 11:44, 2 June 2015
If a custom task is available but is unknown to NairnFEAMPM or NairnFEAMPMViz, you can still use such tasks. In scripted files, an unknown custom task name NewTask is scheduled using the commands
CustomTask NewTask
Parameter Param1,(value1)
. . .
where you provide name of the task and its parameters as required by the task. The name and parameters are all case sensitive (in contrast to known tasks, which may be tolerant of different cases). In XML files, an unknown task is scheduled using a Schedule element, which must be within the single <CustomTasks> block:
<Schedule name='newTask'>
<Parameter name='Param1'>(value2)</Parameter>
. . .
</Schedule>
The use of unknown custom tasks allows you to implement user-written custom tasks. For more details on writing custom tasks, see the help on developing a custom task.