Eric Firing wrote:
> Michael Droettboom wrote:
>> Sorry -- I neglected to commit some changes. (Playing around with
>> bzr and still getting used to it, I guess.)
>
> Very good, thank you!
Phew! For a minute there I thought I was going crazy...
>
> OT: I'm glad you are taking a look at bzr; pers
Michael Droettboom wrote:
> Sorry -- I neglected to commit some changes. (Playing around with bzr
> and still getting used to it, I guess.)
Very good, thank you!
OT: I'm glad you are taking a look at bzr; personally, I chose hg quite
some time ago (when bzr was not mature enough to use), and I
Sorry -- I neglected to commit some changes. (Playing around with bzr
and still getting used to it, I guess.)
Mike
Eric Firing wrote:
> Michael Droettboom wrote:
>> Hmm... works fine for me here, both with the zoom/pan tool and zoom
>> to rect. Can you describe a particular action that isn't
Michael Droettboom wrote:
> Hmm... works fine for me here, both with the zoom/pan tool and zoom to
> rect. Can you describe a particular action that isn't working? I'm at
> a loss otherwise...
Mike,
When I run João's commands in ipython -pylab and click the pan/zoom
button, panning or zoomi
Hmm... works fine for me here, both with the zoom/pan tool and zoom to
rect. Can you describe a particular action that isn't working? I'm at
a loss otherwise...
Mike
Eric Firing wrote:
> Michael Droettboom wrote:
>> Thanks for the reminder. It wasn't propagating the "non-affine"
>> invalid
Michael Droettboom wrote:
> Thanks for the reminder. It wasn't propagating the "non-affine"
> invalidation correctly. I think I have a fix in r6465, but please let
> me know if you see anything else funny.
>
> Cheers,
> Mike
Mike,
It looks like that helps, fixing the window resize behavior,
Thanks for the reminder. It wasn't propagating the "non-affine"
invalidation correctly. I think I have a fix in r6465, but please let
me know if you see anything else funny.
Cheers,
Mike
Eric Firing wrote:
> Mike,
>
> This is a gentle check--I suspect my original message, below, may have
> s
Mike,
This is a gentle check--I suspect my original message, below, may have
slipped under the radar.
Eric
Eric Firing wrote:
> Mike (or other transforms afficionados),
>
> The thread "[Matplotlib-users] Bug saving semilogy plots with a axvline"
> started by [EMAIL PROTECTED] pointed to a bug
Mike (or other transforms afficionados),
The thread "[Matplotlib-users] Bug saving semilogy plots with a axvline"
started by [EMAIL PROTECTED] pointed to a bug that appears to be deep in
the transforms code. My head is spinning. The problem seems to be
related to the propagation of the _inval
