-
Notifications
You must be signed in to change notification settings - Fork 71
Clarify tutorial creates a new msg type #294
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1,5 +1,5 @@ | ||||||||||
| --- | ||||||||||
| title: How to create a new micro-ROS type | ||||||||||
| title: How to create a new micro-ROS message type | ||||||||||
|
FranFin marked this conversation as resolved.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ok
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems similar to my suggestion, which @ralph-lange wasn't happy with. Perhaps "Including a custom ROS message in micro-ROS"? That doesn't imply special support is needed (although I believe with the way ROS 2 and micro-ROS work, it is actually almost like adding support), and does seem to communicate that those are the steps you'd need to get your own custom messages (or someone else's) included in your local micro-ROS build.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like you proposal, @gavanderhoorn! It is short, precise and already implies in the title that the procedure is similar to that for custom message types in normal ROS 2.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, so here it is as a suggestion:
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Only thing is, it doesn't mention services nor actions, so I could see some users getting confused when reading this, but not sure we can help that other than making it clear in the tutorial text itself this is the procedure to follow for those as well.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm ok with @gavanderhoorn suggestion. I assume that @ralph-lange also is. Please @FranFin commit and merge if you are ok. |
||||||||||
| permalink: /docs/tutorials/core/create_new_type/ | ||||||||||
| --- | ||||||||||
|
|
||||||||||
|
|
||||||||||
Uh oh!
There was an error while loading. Please reload this page.