Skip to content

Find and parse .action files as required #23

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

Conversation

chfritz
Copy link
Contributor

@chfritz chfritz commented Jun 13, 2016

  • in addition to .msg and .srv files we can now also require the
    generation of message classes for actionlib files (.action). This
    is in preparation for supporting actionlib as well.

    Example:

rosnodejs.initNode('/my_node', {
  messages: ['std_msgs/String', 'turtlesim/Pose'],
  services: ['std_srvs/SetBool', "turtlesim/TeleportRelative"],
  actions: ['actionlib/TwoInts']
}).then((rosNode) => {
...

Afterwards, the message handler class can be retrieved from the registry like for services:

const action_goal_handler = rosnodejs.require('actionlib').action.TwoInts.Goal;
const action_result_handler = rosnodejs.require('actionlib').action.TwoInts.Result;
const action_feedback_handler = rosnodejs.require('actionlib').action.TwoInts.Feedback;

- in addition to .msg and .srv files we can now also require the
  generation of message classes for actionlib files (.action). This
  is in preparation for supporting actionlib as well.

  Example:

```js
rosnodejs.initNode('/my_node', {
  messages: ['std_msgs/String', 'turtlesim/Pose'],
  services: ['std_srvs/SetBool', "turtlesim/TeleportRelative"],
  actions: ['actionlib/TwoInts']
}).then((rosNode) => {
...
```
@chfritz chfritz closed this Jul 8, 2016
@chfritz chfritz deleted the generate_actionlib_message_types branch September 27, 2016 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant