eeros_architecture:sequencer:usage
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| eeros_architecture:sequencer:usage [2015/10/30 10:47] – [Non Blocking Call of a Sub-Sequence] graf | eeros_architecture:sequencer:usage [2015/10/30 10:48] (current) – removed graf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======Sequencer Usage====== | ||
| - | This page describes the usage of the sequencer in the EEROS framework. | ||
| - | |||
| - | |||
| - | |||
| - | ===== Subsequence===== | ||
| - | A subsequence is a sequence which is called by another sequence. Such a subsequence can be called in a blocking or non-blocking way. Blocking means that the step waits (or blocks) until the subsequence has finished. Non-blocking means that subsequence and main sequence run concurrently. | ||
| - | |||
| - | ====Blocking Call of a Subsequence==== | ||
| - | If you want to save your own data in the sequence, you need to create a new instance of a sequence. This should be done in the desired step (method) of the superior sequence. | ||
| - | e.g. in the method // | ||
| - | |||
| - | <code c> | ||
| - | MyBlockingSubSequence* subSequence = dynamic_cast< | ||
| - | if(!subSequence){ | ||
| - | // | ||
| - | subSequence = new MyBlockingSubSequence(" | ||
| - | } | ||
| - | </ | ||
| - | |||
| - | **Note:** | ||
| - | *In the above lines only one object of // | ||
| - | *It is not allowed to call the // | ||
| - | |||
| - | To start the sub-sequence just call //run()//, which calls all methods in the callback list (filled by // | ||
| - | |||
| - | <code c> | ||
| - | //Here we wait for the returning of the subSequence.run() method | ||
| - | while(subSequence-> | ||
| - | subSequence-> | ||
| - | } | ||
| - | </ | ||
| - | |||
eeros_architecture/sequencer/usage.1446198477.txt.gz · Last modified: 2015/10/30 10:47 (external edit)