-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Add set_offset3d
and get_offset3d
methods to 3D Collections
#27556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
bbd244b
to
a6c2fac
Compare
Only test failure is codecov, but these are fairly well covered and should be fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor style fixes / improvements.
I took the liberty to create a commit with the style fixes. |
8f94462
to
d2b39dd
Compare
Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
070dfab
to
54bd200
Compare
Could you add a simple test? I think just manipulating the values and reading them back to assert that you get the new offesets is sufficient. Or, if you want to be a bit more fancy make an image comparison test where you create a collection in |
Moving back to draft since I need to dig more into what Poly3DCollection is doing |
PR summary
Addresses #784 in part
More discussion in #19573
Note that the inherited
Collection.set_offset
andCollection.get_offset
methods with 2D coordinates are used in zordering calculations and I couldn't see an easy way to abstract those out in order to override those methods and keep the same names as the 2D case.PR checklist