Skip to content

MemSequence bug? #24

@lmessinger

Description

@lmessinger

Hi,

Thanks so much for a VERY comprehensive library. It's a work of art. We like it a lot.

i wonder if there's a bug in MemSequence, when it uses the open() method to reset the 'runningChild' index.

consider a MemSequence with 3 actions children.

  1. action1 starts, return RUNNING for a few ticks
  2. MemSequence is opened (stored at the open node list)
  3. action1 ends, return SUCCESS.
  4. MemSequence is closed
  5. action2 starts, return RUNNING
  6. MemSequence is opened
  7. runningChild is reset to 0!

if thats indeed a bug, i wondered where and when runningChild should be reset? is it a functional decision, based on some other parameters, or should it reset always when it reaches the end of the sequence?

also, what is the use for the openNode list?

thank you for any idea
Lior

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40606176-memsequence-bug?utm_campaign=plugin&utm_content=tracker%2F18331363&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F18331363&utm_medium=issues&utm_source=github).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions