The gist here is that `subplot` doesn't really know when the new subplot
exactly overlaps another -- it's essentially unaware of what's already
there. We could do some deduplication there. However, it's also a
completely legitimate use case to create two subplots in the same
location, and then change the location of the ticks, formatting and
scale on one of them and not the other. And we can't really guess which
the user intends to do. Your workaround seems like a good one, in the
absence of really changing the API here so matplotlib can know the
user's intent.
Mike
On 11/26/2013 08:23 PM, John Gu wrote:
> Hello,
>
> I had submitted a similar issue back in October of 2011. I'm using
> matplotlib 1.3.1. Here's the code to produce the issue:
>
> f = figure()
> for i in xrange(9): subplot(3,3,i+1)
> f.axes[0].plot(range(100))
>
> Now try to drag the line in the first subplot around. It's extremely
> slow. Now do the following:
>
> for ax in f.axes[1:]: ax.axison=False
>
> Now, when you drag the line around in the first subplot, there's a
> huge difference. Basically, it seems like that matplotlib is
> attempting to redraw a lot of unnecessary things on the figure. Is
> there an easy fix to this?
>
> Thanks,
> John
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
--
_
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com
|