Examples: Specify the raycaster recursive flag #22500
Merged
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.
Follow-on to #22460, which changed the default value.
In
raycaster.intersectObjects()
, if therecursive
flag wastrue
, I left it as-is.(Since this is an example, I think it is best to specify the flag -- especially since there has been an API change.)
If the
recursive
flag wasfalse
, I left it as-is.If the
recursive
flag was not specified, I set it tofalse
, because that was the default value prior to #22460.Thing is, I am a bit surprised at the number of
false
settings. Presumably, that is what was intended...