| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| patch.edgecolor : k | ||
| patch.antialiased : True # render patches in antialiased (no jaggies) | ||
|
|
||
| hatch.linewidth : 1.0 |
There was a problem hiding this comment.
Did we have 3 (!) different default values for this before?
Sorry, something went wrong.
There was a problem hiding this comment.
Actually 4, since SVG was "1 point" and Agg was "1 pixel". We could try to emulate that old brokenness if we want (I guess).
Sorry, something went wrong.
There was a problem hiding this comment.
No, I think unify on one is an ok complete break. We should at least document what the old values were. On the off chance we get someone who really cares, they likely only care on one backend (or we would have heard from them sooner!).
Sorry, something went wrong.
There was a problem hiding this comment.
Agreed. I've documented the old values in the style changes what's new.
Sorry, something went wrong.
| Op.fill) | ||
|
|
||
| self.output(0.1, Op.setlinewidth) | ||
| self.output(rcParams['hatch.strokewidth'], Op.setlinewidth) |
There was a problem hiding this comment.
should this be hatch.linewidth?
Sorry, something went wrong.
There was a problem hiding this comment.
Indeed. Will fix. Puzzled by why that didn't raise an exception.
Sorry, something went wrong.
|
Passing Travis. AppVeyor seems blocked for last 3 hours. |
Sorry, something went wrong.
|
I think this is up next, but for some reason, AppVeyor only seems to be building one part of the matrix at a time. |
Sorry, something went wrong.
| Op.fill) | ||
|
|
||
| self.output(0.1, Op.setlinewidth) | ||
| self.output(rcParams['hatch.linewidth'], Op.setlinewidth) |
There was a problem hiding this comment.
How significant of a performance hit is it to be constantly re-querying this dictionary?
Also, is it the right thing to access the rcParams this late in the draw process? We are pretty bad at being consistent, but I don't recall doing this sort of rcParam access this late anywhere else. What if someone uses an rc context to set up the hatches, but the savefig call is outside that context?
Sorry, something went wrong.
There was a problem hiding this comment.
Fair point on being consistent, but there is currently no other API to change this value. The main reason for getting this PR in for 2.0 is to put as rcparam in so we can change it and provide a way to get back to the old version. Adding a proper API for changing this can be done later as a new feature and at that point it should be set at artist creation time, not draw time.
Sorry, something went wrong.
|
I am happy to merging this as-is to move 2.0 along. This improves things, there is now a way to change the hatch width and it is uniform across all of the backends (that we control) and closes a 3 digit bug! Still to do are:
@mdboom This has one overlap with the test images in the tick centering PR, maybe we should stack them into one merge? |
Sorry, something went wrong.
|
I think the axes spacing in #6129 will also touch many test images and maybe should be folded in as well if you're going to do so already. |
Sorry, something went wrong.
|
@tacaswell wrote:
Sure -- not sure how best to do that, though. |
Sorry, something went wrong.
|
rebase one of them on the other? |
Sorry, something went wrong.
|
I think we should just merge this and #6200 separately. It's sort of rebase hell to pull out the test images from this one -- plus it will make bisecting harder later. |
Sorry, something went wrong.
|
fair enough. |
Sorry, something went wrong.
ENH/API: Make hatch linewidth an rcParam This also changes the default hatch width on some backends.
| Back | FazBrowse Home | New Git URL |
Fix #235