Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Let quiver retrieve X, Y from base PolyCollection.get_offsets().#24952
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 ourterms of service andprivacy 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?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
... instead of additionally storing copies locally in`self.X, self.Y, self.XY` (for quiver), `self.x, self.y` (for barbs).Then there's no reason not to also suggest set_offsets in quiver(), likeit's already done in barbs().
orientation, and color of the arrows. Locations are changed using the | ||
(inherited) `.PolyCollection.set_offsets` method. This method may be | ||
useful in animations. |
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.
Unfortunately I think the behavior is a little bit more complicated than than just usingset_offsets
due to the interactions of UVC and XY which may be difficult for users to discover. See#22407
Ah, sorry I missed your PR. Let's put this on hold first. |
... instead of additionally storing copies locally in
self.X, self.Y, self.XY
(for quiver),self.x, self.y
(for barbs).Then there's no reason not to also suggest set_offsets in quiver(), like it's already done in barbs().
PR Summary
PR Checklist
Documentation and Tests
pytest
passes)Release Notes
.. versionadded::
directive in the docstring and documented indoc/users/next_whats_new/
.. versionchanged::
directive in the docstring and documented indoc/api/next_api_changes/
next_whats_new/README.rst
ornext_api_changes/README.rst