PLYLoader: Fix comments. #25578
Merged
PLYLoader: Fix comments. #25578
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
PLYLoader: Edit a typo in file comment.
Mugen87
approved these changes
Feb 27, 2023
This pull request was closed.
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.
PLYLoader: Update a code comment.
Description
This PR updates a code comment that was causing confusion regarding the use of setCustomPropertyMapping. The comment suggested that this method was used with PLYLoader, but PLYLoader does not have a setCustomPropertyMapping method. Instead, setCustomPropertyNameMapping can be used with PLYLoader to set custom property name mappings.
To address this issue, the comment has been updated to clarify the usage of setCustomPropertyNameMapping.