Differences

This shows you the differences between two versions of the page.

--- eeros_architecture:sequencer:define_sequence [2019/03/06 10:40] – [Write your own Class] graf
+++ eeros_architecture:sequencer:define_sequence [2019/03/14 10:27] – [Waiting in Sequences or Steps] graf
@@ Line 18: / Line 18: @@
 </code>
 Your constructor usually includes a name for the sequence or step, a reference to the sequencer, and a reference to the caller of this object. The latter point is very important, because every step or sequence must know its caller or owner. \\
-You then initialize the sequence in the initializer list by writing ''Sequence(name, seq, caller, false)''. The last parameter defines whether your sequence is blocking or nonblocking. Setting to blocking (''false'') makes this sequence block its calling sequence, setting to nonblocking (''true'') starts a new thread which runs the sequence in parallel to its calling sequence. A step is always blocking.
+You then initialize the sequence in the initializer list by writing ''Sequence(name, seq, caller, false)''. The last parameter defines whether your sequence is blocking or nonblocking. Setting to blocking (''true'') makes this sequence block its calling sequence, setting to blocking (''false'') starts a new thread which runs the sequence in parallel to its calling sequence. A step is always blocking.
 In the body of your constructor you define the attributes of your sequence. This includes:
@@ Line 123: / Line 123: @@
 </code>
 This step simply takes a time stamp when running its action method. Its exit condition becomes ''true'' as soon as a waiting time of 3.2s has elapsed. However, contrary to a simple //sleep// it does not block the sequencer and the checking of monitors of this step or sequence continues unhindered.
+===== Returning Values =====