Add "copy_all_fields" option to transformPointCloud***() functions #805
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So far different transform functions had inconsistend behavior. Some copied the data in all fields, some did not. Following the discussion in PointCloudLibrary#575, this commit adds an option to control the copy behavior.
|
This looks good, but I think it changes the ABI, so I would propose to postpone it for 1.8. |
|
No problem. |
jspricke
added a commit
that referenced
this pull request
Sep 11, 2014
Add "copy_all_fields" option to transformPointCloud***() functions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So far different transform functions had inconsistent behavior. Some copied the data in all fields, some did not. Following the discussion in #575, this commit adds an option to control the copy behavior. "Copy all" is used as default since it is intuitive.
Closes #575.