Skip to content
New issue

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

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

Already on GitHub? # to your account

Add option to start with a topic selected #20

Closed
sea-bass opened this issue Apr 19, 2021 · 0 comments · Fixed by #21
Closed

Add option to start with a topic selected #20

sea-bass opened this issue Apr 19, 2021 · 0 comments · Fixed by #21

Comments

@sea-bass
Copy link
Contributor

sea-bass commented Apr 19, 2021

For demo launching purposes, it would be nice to start rqt_py_trees with an optional argument that specifies the topic name to start subscribing to. For example, either or both of these:

rqt_py_trees --topic /my_node/log/tree
rosrun rqt_py_trees topic:=/my_node/log/tree

Otherwise, even if you make a launch file that automatically launches rqt_py_trees, users have to manually change the topic drop-down to the right topic.

The behavior could either be to wait for the desired topic to send a message, or if the topic isn't available to assume "none" and open rqt_py_trees as normal.

@sea-bass sea-bass changed the title Add Topic Name Option to Launch File Add option to start with a topic selected Apr 19, 2021
stonier added a commit that referenced this issue May 9, 2021
Pretty messy logic therin. Now prioritises

* Command Line
* Saved and valid
* First valid
* Saved
* Pending

NB: It won't automatically switch when it finds something - it will
adhere to the logic the user has provided (either via the command line
or via a saved preference).

Resolves #20
stonier added a commit that referenced this issue May 9, 2021
Pretty messy logic therin. Now prioritises

* Command Line
* Saved and valid
* First valid
* Saved
* Pending

NB: It won't automatically switch when it finds something - it will
adhere to the logic the user has provided (either via the command line
or via a saved preference).

Resolves #20
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant