Hi,
I have fixed the double-zoom Bug in the trunk (revision 5053), but
not in the 0_91maint branch. In 0.91 it's not so easy to find out
whether an axes is shared with another (cbook:Group is nice ;-) ) For
0.91: is it always guaranteed that the release_zoom event for the master
is called b
On Mon, Apr 7, 2008 at 8:38 AM, Manuel Metz <[EMAIL PROTECTED]> wrote:
> The problem is that "release_zoom" in backend_bases.py is called twice in
> the above case if zoomed to a twinx'ed plot. One way to fix this behavior is
> to set a "twin" attribute to the axes instance. Attached is a patch a
On 20/04/2008, Eric Firing <[EMAIL PROTECTED]> wrote:
> > Odd, I'm using matplotlib 0.98pre (svn) with GTKAgg (gtk 2.12.8, pygtk
> >
> Very odd. Would you try writing out postscript and pdf, please, and see
> whether they behave the same way?
The contour lines are still visible:
http://mentat.z
Stéfan van der Walt wrote:
> On 20/04/2008, Eric Firing <[EMAIL PROTECTED]> wrote:
>>> Odd, I'm using matplotlib 0.98pre (svn) with GTKAgg (gtk 2.12.8, pygtk
>>>
>> Very odd. Would you try writing out postscript and pdf, please, and see
>> whether they behave the same way?
>
> The contour lines
On 20/04/2008, Eric Firing <[EMAIL PROTECTED]> wrote:
> I don't see any contour lines; I see only the boundaries between patches.
> In other words, the plot looks the way I would expect it to. This is with
> evince or gv on a linux machine. (Both fail when trying to blow up the plot
> to 400%, bu
And the attachment...
On 20/04/2008, Eric Firing <[EMAIL PROTECTED]> wrote:
cef.py
Description: Binary data
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's
Stéfan,
OK, I see some differences now, and it looks like it is related to
antialiasing and the rendering of patch boundaries. I have run into
this sort of thing before, where depending on how patch edges are
handled, and depending on the particular renderer and viewer
combination, antialiasi
