mtaskext.tasksem.tex

   1 The current \gls{mTask} engine for devices does not support \glspl{Task} in the
   2 sense that the \gls{C}-view does. \Glspl{Task} used with the \gls{C}-view are a
   3 main program that executes code and launches \glspl{Task}. It was also possible
   4 to just have a main program. The current \gls{mTask}-system only supports main
   5 programs. Sending a \gls{Task} always goes together with choosing a scheduling
   6 strategy. This strategy can be one of the following three strategies:
   7
   8 \begin{itemize}
   9         \item\CI{OneShot}
  10
  11                 \CI{OneShot} takes no parameters and means that the \gls{Task} will run
  12                 once and will then be removed automatically. This type of scheduling
  13                 is useful, for example, in retrieving sensor information on request of
  14                 the user.
  15         \item\CI{OnInterval}
  16
  17                 \CI{OnInterval} has the number of milliseconds to wait in between
  18                 executions as a parameter. \Glspl{Task} running with this scheduling
  19                 method are executed at predetermined intervals.
  20         \item\CI{OnInterrupt}
  21
  22                 The last scheduling method is running \glspl{Task} on a specific
  23                 interrupt. Unfortunatly, due to time constraints and focus, none of the
  24                 current client implementations support this. Interrupt scheduling is
  25                 useful for \glspl{Task} that have to react on a certain type of
  26                 hardware event such as the press of a button.
  27 \end{itemize}