On Fri, Jul 25, 2008 at 5:23 AM, David Kaplan <[EMAIL PROTECTED]> wrote:
> I have committed to SVN the change making twinx work like twiny. As an
> aside, this would not be necessary if there was an easy after the fact
> way of sharing and unsharing axes (i.e., ax.set_shared_x_axes(ax2)).
Yes, the sharex attr should be set on twinx -- perhaps someone
commented this out while debugging and forgot to restore it. I have
been known to make this mistake on more than one occasion, so thanks
for catching it. As for the duplicated ticklabels, I think we should
make the ticklabels invisible for ax2
for tick in ax2.xaxis.get_major_ticks() + ax2.get_minor_ticks():
tick.set_visible(False)
Are there any potential problems with this that you can see?
Obviously we would want to document and mention it in the CHANGELOG,
because it might affect some code that is using the twin axes to
configure tick labels, but it should be an easy fix for those users to
simply use the original axes and it will get it right in most cases
(no duplicate labels or ticks).
I agree that being able to set the sharex and sharey after the fact
would be useful.
JDH
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
