-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Log pixel coordinates in event_handling coords_demo example on terminal/console #21389
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
Conversation
Hi, thanks for the PR! Please edit your post to add a short summary of why you're making these changes. |
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.
Thank you for opening your first PR into Matplotlib!
If you have not heard from us in a while, please feel free to ping @matplotlib/developers
or anyone who has commented on the PR. Most of our reviewers are volunteers and sometimes things fall through the cracks.
You can also join us on gitter for real-time discussion.
For details on testing, writing docs, and our review process, please see the developer guide
We strive to be a welcoming and open project. Please follow our Code of Conduct.
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.
I think this is actually helpful. Thanks!
thanks @story645 for help. i have added the summary. hope it explains role of my PR. |
Congrats on the PR, hope to see you again! 🎉 |
Yeah definitely @story645 😊 |
Log pixel coordinates in event_handling coords_demo example on terminal/console
PR Summary
coords_demo.py example has unused variables for pixel values. This PR attempts to improve this by logging pixel value, alongside axis data on the terminal/console where this specific example is running
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).