-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
Fix use of scaling in vispy points #6894
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6894 +/- ##
==========================================
- Coverage 92.45% 92.44% -0.02%
==========================================
Files 614 614
Lines 55164 55164
==========================================
- Hits 51001 50994 -7
- Misses 4163 4170 +7 ☔ View full report in Codecov by Sentry. |
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.
This fixes the point-size issue in the description which I also bumped into in #6914.
Code changes also look fine, as I understand that we want point sizes to only be dependent on Points.size
and not Points.scale
.
I don't see any wobble on main
with the given example, so I cannot vouch for that. Maybe I'll defer to @psobolewskiPhD on that?
This is what I see on main with the code above (fresh env, ensure vispy's up to date): Peek.2024-05-15.10-28.mp4 |
My env was a fresh napari dev install. But I was able to reproduce now, but only when I'm zoomed out. |
Should be good to go then :) |
References and relevant issues
In #6025, the vispy update broke the efforts from #5312. This is actually because the changes in vispy apparently do not handle the
scaling
kwarg properly at initialization. We can fix it here by not passing it.I can't believe this has been wrong for so long, and I somehow never connected this issue that kept bugging me with that PR... but here we are.
Description
Try the following on main and here and move the camera around:
This fixes two things:
This returns to the correct, pre-#6025 situation.