Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Jointly track x and y in PolygonSelector.#21894
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Can we wait until#21830 is merged for this to go in? |
Sure, sorry, I had only noticed#21881 as potentially conficting. |
Thanks for the notification, rebased. |
Seems to have broken some things. |
Thanks, I missed a point when rebasing over#21830. |
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.
Much nicer, thanks a lot! This approval is contingent on CI passing.
It's easier to track them in a single list.Also init _selection_artist and _polygon_handles with empty arrays, asthere's no reason to pretend that they start with 0, 0. On the otherhand, _xys does need to start as a non-empty array as the last pointgets updated as being the cursor position.
Uh oh!
There was an error while loading.Please reload this page.
It's easier to track them in a single list.
Also init _selection_artist and _polygon_handles with empty arrays, as
there's no reason to pretend that they start with 0, 0. On the other
hand, _xys does need to start as a non-empty array as the last point
gets updated as being the cursor position.
PR Summary
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).