Fixed Example for custom Point Type #5020
Merged
Conversation
This file contains hidden or 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
Member
|
Thanks! |
okinaka
added a commit
to okinaka/docs
that referenced
this pull request
Jun 21, 2017
Merged
okinaka
added a commit
to okinaka/docs
that referenced
this pull request
Jun 23, 2017
okinaka
added a commit
to okinaka/docs
that referenced
this pull request
Jun 23, 2017
HavokInspiration
added a commit
that referenced
this pull request
Jun 23, 2017
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Without this change the user will get an "Call to a member function types() on float" (or string or whatever).
The Values must be passed as array to the second parameter of FunctionExpression;
until now they are passed in the example as second and third, which lead to interpreting the second value as "type".