On Monday 30 June 2008 09:01:48 John Hunter wrote:
> On Mon, Jun 30, 2008 at 3:32 AM, Andrea Gavana <[EMAIL PROTECTED]>
wrote:
> > It seems like Michael changes were reverted back to the previous
> > behaviour. I have scanned the matplotlib-devel archives and found the
> > reason. Even if the mess
On Mon, Jun 30, 2008 at 3:32 AM, Andrea Gavana <[EMAIL PROTECTED]> wrote:
> It seems like Michael changes were reverted back to the previous
> behaviour. I have scanned the matplotlib-devel archives and found the
> reason. Even if the message says that text.py is fixed, I still see
> the problem I
Hi All,
On 6/27/08, Andrea Gavana wrote:
> Hi Michael,
>
> On Fri, Jun 27, 2008 at 7:54 PM, Michael Droettboom wrote:
> > Andrea Gavana wrote:
> >>
> >> 2) The dashed text positioning is wrong, you can see it by running
> >> dashpointlabel.py in the
> >> matplotlib_examples_0.98.1\examples\pylab_e
Hi Michael,
On Fri, Jun 27, 2008 at 7:54 PM, Michael Droettboom wrote:
> Andrea Gavana wrote:
>>
>> 2) The dashed text positioning is wrong, you can see it by running
>> dashpointlabel.py in the
>> matplotlib_examples_0.98.1\examples\pylab_examples: the position of
>> the values should be at the o
Andrea Gavana wrote:
> 2) The dashed text positioning is wrong, you can see it by running
> dashpointlabel.py in the
> matplotlib_examples_0.98.1\examples\pylab_examples: the position of
> the values should be at the other end of the dash, not over the
> plotted point.
>
>
I believe I have this
Andrea Gavana wrote:
> Hi All,
>
> I have switched from matplotlib 0.91.2 to 0.98.1, and I have
> noticed a couple of "strange" behaviours (I am not using PyLab, but
> matplotlib embedded in wxPython):
>
> 1) If I use:
>
> ylims = self.myAxis.get_ylim()
>
> And then I add other lines to the plo
