| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Would you be able to turn your example code above into an image test so that we don't break this in the future? |
Sorry, something went wrong.
|
@pharslap, looks great. I took the liberty of editing your title - no need to ref original issue, and description of fix is most helpful... |
Sorry, something went wrong.
@dopplershift I have added a test that doesn't use image comparison. |
Sorry, something went wrong.
|
@WeatherGod @efiring Could you please take a look at this? Tagging you since you were involved in the discussion on the issue. Thanks! |
Sorry, something went wrong.
|
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... |
Sorry, something went wrong.
Ok. Thanks for taking a look! |
Sorry, something went wrong.
|
@efiring - still investigation 😉 I'll assume this can wait for 3.2... |
Sorry, something went wrong.
|
Sorry for the long delay. I will try to take care of this as soon as #6268 goes in. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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