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

Use only a single ros node inside of rviz #197

Merged
merged 11 commits into from
Jun 12, 2018

Commits on Jun 12, 2018

  1. Configuration menu
    Copy the full SHA
    1f520ac View commit details
    Browse the repository at this point in the history
  2. Return a node abstraction from ros clients init

    - No longer uses the node_name as indirect handle to the node.
    - The interface of node abstraction is not yet extended, also for now
      still only the node name is handed to the VisualizationFrame.
    - The ros client abstraction internally holds a shared pointer to the
      "one" rviz ros node (in form of a RosNodeAbstraction). Users only
      receive a weak pointer to the RosNodeAbstraction so that the
      RosClientAbstraction can perform a proper cleanup upon shutdown.
    - Make documentation comments describe reality.
    anhosi committed Jun 12, 2018
    Configuration menu
    Copy the full SHA
    2891704 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    a808675 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    d2929bc View commit details
    Browse the repository at this point in the history
  5. Store the rclcpp::Node inside the RosNodeAbstraction

    - Intended usage: rviz should have only a single instance of
      RosNodeAbstraction to manage all node related ros interaction.
    - So there is no need to handle many node. Thus RosNodeStorage can be
      removed.
    anhosi committed Jun 12, 2018
    Configuration menu
    Copy the full SHA
    648f0af View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    3822108 View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    547e13e View commit details
    Browse the repository at this point in the history
  8. Use only the single ros node of rviz

    - All of rviz now uses only a single ros node.
    - As the abstraction for subscriptions is not yet present the wrapped
      raw rclcpp::Node has to be access in order to subscribe. This will be
      addressed in the future.
    anhosi committed Jun 12, 2018
    Configuration menu
    Copy the full SHA
    4f2de89 View commit details
    Browse the repository at this point in the history
  9. Cleanup

    anhosi committed Jun 12, 2018
    Configuration menu
    Copy the full SHA
    c1c7248 View commit details
    Browse the repository at this point in the history
  10. Remove add_to_executor from node interface as it is not needed

    - The main rviz node is added to the main executor at application
      start
    - Further interaction with the executor should not be necessary
    anhosi committed Jun 12, 2018
    Configuration menu
    Copy the full SHA
    b3f401b View commit details
    Browse the repository at this point in the history
  11. Cleanup: consistent naming

    anhosi committed Jun 12, 2018
    Configuration menu
    Copy the full SHA
    49e9107 View commit details
    Browse the repository at this point in the history