Skip to content

Improve documentation on ReactiveSequence #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 25, 2024
Merged

Improve documentation on ReactiveSequence #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions docs/nodes-library/SequenceNode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,9 @@ Let's take a look at another example:
`ApproachEnemy` is an __asynchronous__ action that returns RUNNING until
it is, eventually, completed.

The condition `isEnemyVisible` will be called many times and,
if it becomes false (i,e, "FAILURE"), `ApproachEnemy` is halted.
The __synchronous__ condition `isEnemyVisible` will be called many times and
returns true or false quickly. If it becomes false (i,e, "FAILURE"), `ApproachEnemy`
is halted.


## SequenceWithMemory
Expand All @@ -72,6 +73,3 @@ On the other hand, __isBatteryOK__ must be checked at every tick,
for this reason its parent must be a `ReactiveSequence`.

![SequenceWithMemory](images/SequenceStar.svg)