Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Change layout of test_triager to avoid cropping images. #15261

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

Merged
merged 1 commit into from
Sep 13, 2019

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Sep 12, 2019

The previous test triager would crop test images because the 800/500
aspect ratio of the main widget does not match the 6.4:4.8 aspect ratio
of the test images. Change the main widget to have size 800x600, and
move the thumbnails to the side so that the whole thing still fits in a
1600x900 display.

before
old
after
new
(yes, this is the whole test image, the ylabels are actually cropped)

PR Summary

PR Checklist

  • Has Pytest style unit tests
  • Code is Flake 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

The previous test triager would crop test images because the 800/500
aspect ratio of the main widget does not match the 6.4:4.8 aspect ratio
of the test images.  Change the main widget to have size 800x600, and
move the thumbnails to the side so that the whole thing still fits in a
1600x900 display.
@tacaswell tacaswell added this to the v3.3.0 milestone Sep 13, 2019
@tacaswell tacaswell merged commit 2aba5aa into matplotlib:master Sep 13, 2019
@tacaswell
Copy link
Member

This has been annoying me for a while, but not enough to do something about it, thanks @anntzer !

@anntzer anntzer deleted the triager-layout branch September 13, 2019 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants