|
From: Ryan N. <rne...@gm...> - 2013-10-29 02:11:22
|
Daniele, I noticed the same problem with the Qt backend. However, I was looking at the documentation on the AxesGrid webpage here: http://matplotlib.org/mpl_toolkits/axes_grid/users/overview.html And I see the following warning: axes_grid and axisartist (but not axes_grid1) uses a custom Axes class (derived from the mpl’s original Axes class). As a side effect, some commands (mostly tick-related) do not work. Use axes_grid1 to avoid this, or see how things are different in axes_grid and axisartist (LINK needed) Unfortunately, no link. But perhaps there is a way to avoid using the Axes class from axisartist in your use case. For example, could you import the Axes class as follows: from matplotlib.axes import Axes That seems to work with the Qt and PDF backends on Windows 7 (Anaconda Python). Ryan On Mon, Oct 28, 2013 at 7:37 PM, Daniele Nicolodi <da...@gr...>wrote: > On 29/10/2013 00:17, Sterling Smith wrote: > > While your example tries to be self contained, which is great!, there is > no difference between these two conditions... > > > >> if BUG: > >> ax1 = host_subplot(111, axes_class=Axes) > >> else: > >> ax1 = host_subplot(111, axes_class=Axes) > > Ops, obvious mistake. It should read: > > BUG = True > if BUG: > ax1 = host_subplot(111 , axes_class=Axes) > else: > ax1 = host_subplot(111) > > > Cheers, > Daniele > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > |