direct: Use explicitly Vec3F in calls to addData3f to avoid crash on double precision builds #1365
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.
Issue description
When opening the BufferViewer with Panda3D compiled with double precision float enabled, the app crashes as
Vec3
is actuallyVec3D
andaddData3f()
expectVec3F
Solution description
Trivial fix that replace
Vec3
withVec3F
Checklist
I have done my best to ensure that…