fix(WebXRManager): setAnimationLoop should accept null like WebGLRenderer #158
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.
Why
WebXRManager#setAnimationLoop
is called internally byWebGLRenderer#setAnimationLoop
to update camera and controller internals with the viewer's pose. Although they are passed the same callback, only WebGLRenderer's signature will accept null for a callback. There, a falsy value will stop the internal animation used to drive the animation loop. WebXRManager will only start/stop when sessions init/end but will respect WebGLRenderer's signature as it is called internally.What
I've updated WebXRManager's signature to match.
Checklist