-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
FIX: pcolor/pcolormesh honour edgecolors kwarg when facecolors is set 'none' #12226
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: pcolor/pcolormesh honour edgecolors kwarg when facecolors is set 'none' #12226
Conversation
Would you be able to turn your example code above into an image test so that we don't break this in the future? |
@pharslap, looks great. I took the liberty of editing your title - no need to ref original issue, and description of fix is most helpful... |
@dopplershift I have added a test that doesn't use image comparison. |
@WeatherGod @efiring Could you please take a look at this? Tagging you since you were involved in the discussion on the issue. Thanks! |
I'm pretty sure this is not the right solution. It looks like there is a simple underlying bug that this is not addressing. Investigating... |
Ok. Thanks for taking a look! |
@efiring - still investigation 😉 I'll assume this can wait for 3.2... |
Sorry for the long delay. I will try to take care of this as soon as #6268 goes in. |
This is superseded by #18480. Thank you for the contribution, @pharshalp. Although your PR was not merged, it led to a different solution to the problem. |
PR Summary
Closes #1302
This fixes the issue #1302 [edgecolor(s) being ignored by pcolor/pcolormesh when facecolor(s) is set to 'none'].
From a quick look at the discussion in #1302 and looking at the underlying code, I think this PR should work.
NOTE: I am not entirely familiar with how the Collection object is supposed to behave. If this PR fails the tests then I will close this PR and dig deeper to find the correct approach.(all the tests passed!).Example:
Current outcome:

Correct outcome (after applying the fix in this PR):

PR Checklist
[ ] New features are documented, with examples if plot related[ ] 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