Skip to content
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.

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

Improvements for visualisation #331

Open
stonier opened this issue May 27, 2021 · 0 comments
Open

Improvements for visualisation #331

stonier opened this issue May 27, 2021 · 0 comments

Comments

@stonier
Copy link
Member

stonier commented May 27, 2021

The display module has a few problems.

Must-solve

  • The updated status of each and every ticked behaviour must be reflected for visualisation purposes and not lost. This currently occurs when composites / decorators invalidate behaviours after the behaviour tick but before visualisation for logistical reasons to avoid dangling runners. Refer to Loss of visibility when invalidating #132 for an example.

Nice-to-haves

  • Differentiate between not-ticked and ticked parts of the tree (e.g. gray unticked, white ticked, cyan tip). Only relevant for unicode tree display methods (py_trees_js already does this).
  • A toggle to show the last non-invalid status for behaviours, even beyond the last tick.

Potential Solution

Do logistical cleanup just prior to ticking the tree (might be expensive / awkward) OR cache the last non-invalid status and use that as the status to visualise for ticked behaviours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant