René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Modified axes patch will not re-clip artists","articleBody":"This probably doesn't come up too much since most people plot in Cartesian, but I've run into it working on #4699. Artists are only clipped to whatever the patch looked like at the time that the artist was added to the axes. I have tracked down the issue and just want determine the best way forward.\n\nThe problem arises from the fact that axes use a `Patch` for the background and default clipping definitions while artists use a `Path` for actual clipping. To get this `Path`, the path and transform are pulled from the `Patch` and placed in a `TransformedPath`. This is all well and good for Cartesian axes with rectangles, because they're always unit squares where only the transform is changed. But as part of #4699, the `PolarAxes` use a `Wedge` and every time parameters are changed, a new `Path` is calculated. This new `Path` has no link to the `TransformedPath` used by any existing `Artist`s and they end up clipping using some old version. The user could get around this by plotting only after setting all the limits for the axes, but I find that less than ideal.\n\nSo the question is how to remedy this issue. I see a couple options:\n- `Wedge` always returns the same `Path` object, but just changes the underlying vertices/codes. I don't see that `Path` provides an easy way to do so though.\n- Add a `TransformedPatch` analogue to `TransformedPath`.\n\nThat being said, I'm not sure how the clipping path would get informed that the underlying (untransformed) `Patch` or `Path` was modified since only `Transforms` have that invalidation code (or maybe I missed something for it.)\n","author":{"url":"https://github.com/QuLogic","@type":"Person","name":"QuLogic"},"datePublished":"2015-07-25T08:45:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/4788/matplotlib/issues/4788"}