matplotlib-users Mailing List for matplotlib

On Thu, Apr 22, 2010 at 4:44 PM, Carlos Grohmann
<car...@gm...>wrote:
> Hi all,
>
> I'm getting this weird behavior of legend. I always get two symbols in
> front of the labels, instead of one.
> Did anyone experienced this before?
>
> I'm working with MPL in a WxPython app.
>
> code snippet:
>
>
> [code]
> for i in range(len(self.idxPlan)):
> x = self.PeigenList[i][14] + (self.PeigenList[i][15] / 2)
> y = self.PeigenList[i][15] * sqrt3_2
> axes.plot(x,y, self.PProps[i][3], c=self.PProps[i][2],
> ms=self.PProps[i][4],label=self.Pname[i])
>
> axes.legend(bbox_to_anchor=(0.85, 0.75), loc=2,
> prop=FontProperties(size='small'))
>
> axes.set_xlim(-0.1,1.2)
> axes.set_ylim(-0.1,1.2)
> self.dataCanvas.draw()
>
> [\code]
>
>
> tks
> --
> Prof. Carlos Henrique Grohmann - Geologist D.Sc.
> Institute of Geosciences - Univ. of São Paulo, Brazil
> http://www.igc.usp.br/pessoais/guano
> Linux User #89721
> ________________
> Can’t stop the signal.
>
Hi,
Try using numpoints keyword:
plt.legend(numpoints=1)
-- 
Gökhan

Hi all,
I'm getting this weird behavior of legend. I always get two symbols in
front of the labels, instead of one.
Did anyone experienced this before?
I'm working with MPL in a WxPython app.
code snippet:
[code]
 for i in range(len(self.idxPlan)):
 x = self.PeigenList[i][14] + (self.PeigenList[i][15] / 2)
 y = self.PeigenList[i][15] * sqrt3_2
 axes.plot(x,y, self.PProps[i][3], c=self.PProps[i][2],
ms=self.PProps[i][4],label=self.Pname[i])
 axes.legend(bbox_to_anchor=(0.85, 0.75), loc=2,
prop=FontProperties(size='small'))
 axes.set_xlim(-0.1,1.2)
 axes.set_ylim(-0.1,1.2)
 self.dataCanvas.draw()
[\code]
tks
-- 
Prof. Carlos Henrique Grohmann - Geologist D.Sc.
Institute of Geosciences - Univ. of São Paulo, Brazil
http://www.igc.usp.br/pessoais/guano
Linux User #89721
________________
Can’t stop the signal.

Hello,
Consider my simple test case:
import matplotlib.pyplot as plt
fp = plt.figure()
ax1 = fp.add_subplot(4,1,1)
ax1.plot(range(10))
ax2 = fp.add_subplot(4,1,2)
ax2.plot(range(10))
ax1.xaxis.set_major_locator (plt.NullLocator ())
ax3 = fp.add_subplot(4,1,3)
ax3.plot(range(10))
# Can't turn off
ax3.xaxis.set_major_locator (plt.NullLocator ())
ax4 = fp.add_subplot(4,1,4, sharex=ax3)
ax4.plot(range(10))
# Turn-off both ax3 and ax4
#ax3.xaxis.set_major_locator (plt.NullLocator ())
plt.show()
When I share x-axis in between two plots I can't turn-off one axis' major
ticks. Depends on the location of the function call it either turn nothing
or all. Is it intended or a mal-functioning? (Shared axis is for my screen
view, I can live without it by turning off sharex option since it won't make
any difference for the final saved figures.)
Thanks.
-- 
Gökhan

If I rotate an axes3D instance with a zlabel
far enough so that the ticks and label "switch sides",
but so that the xlabel and ylabel remain at the bottom,
then the zlabel does not rotate 180 degrees,
as it should to look right. (If I then tilt it so
that the xlabel and the ylabel move to the top,
it does the necessary rotation.)
Alan Isaac

On Thu, Apr 22, 2010 at 3:42 AM, Matthias Michler
<Mat...@gm...>wrote:
> Hi Gökhan,
>
> Just to make one point clear to me. Do you agree that the following is the
> expected behavior of your suggestion to use
> event.inaxes.grid(which='minormajor') after 'g'?
>
> If only the major tick grid lines are shown and the user presses 'g' the
> major
> tick lines are removed and the minor tick lines are shown, because calling
> Axes.grid with the default b=None toggles the state of plotting grid lines.
> Here this means that the minor tick grid lines are switched from being not
> shown to being shown and the major tick lines change vice versa.
>
> If you agree that this is the expected behavior of your suggestion, do you
> think this is a useful behavior?
>
> Kind regards,
> Matthias
>
Hi again,
With grid state initially off I could get what I really wanted with "g"
toggling after setting in backend_bases.py
event.inaxes.grid(which='majorminor)
It does exactly what it supposed to do -toggle visible grids. See my figure
for a clearer description:
http://img249.imageshack.us/img249/1464/gridimage.png
The top-left figure has major-minor grids enabled in log-log view. This
creates not a pretty image --neither on screen nor when I save the image as
png or pdf. Top-right is clear since it is spaced linearly. The last figure
I toggled with "g" key. It was originally like the first figure on the
screen. I realize also that grid accept alpha keyword, however I couldn't
get a satisfying result out of that either. For the time being I will go
with full-off grids for my step plots.
With this said, I still think event.inaxes.grid(which='majorminor) should be
checked-in since it is the right behavior for full grid toggling. That's
what toggling is about right? Either all or none --we don't want gray areas.
>
-- 
Gökhan

On Thu, Apr 22, 2010 at 3:25 AM, Matthias Michler
<Mat...@gm...>wrote:
> Hi Gökhan,
>
> with the attached test.py I generated the attached files 'pic?.png' and I'm
> sorry, I don't get the problem. For me ax.grid(False, which='majorminor')
> removes major and minor ticks on x- and y-axis.
>
> Maybe I changed something additionally in my svn (rev 8242) and therefore
> get
> the expected behavior. But unfortunately I cannot test it today.
>
> Kind regards,
> Matthias
The problem was on my side Matthias. I had enabled grid=True in my
matplotlibrc file. Turned it off and I get the same behavior as you get.
Thanks for providing the script and comments.
-- 
Gökhan

Actually which backend are you using? I'd like to try this to see what happens if show() is called more than once.
--Michiel.
--- On Tue, 4/20/10, Antony Lee <ant...@en...> wrote:
That would be a solution, indeed. However, is there really no way of coming back to a pre-plt.show() state once all windows are closed? What kind of irreversible things does plt.show() do?