matplotlib-devel Mailing List for matplotlib

On Thu, Jul 22, 2010 at 9:46 PM, Eric Firing <ef...@ha...> wrote:

> On 07/22/2010 04:34 PM, Benjamin Root wrote:
> > Heh, looks more pervasive than just the Tkinter backend, and it isn't
> > just caused by zooming.  Just moving the image off to the side is
> > enough, and saving that figure using the "Save" button produces this
> > attached image.
> >
> > And further testing shows that this occurs if I manually set my limits
> > before the .show() call and save using .savefig()
> >
> > Attached is a simple script.
>
> Running your script, I don't see any artifacts with gtkagg or with
> tkagg, or if I save the file to png.  I'm also running with latest svn.
>
> I wonder whether your installation has gotten scrambled?  You might try
> deleting your build directory and your installed mpl, then rebuild and
> reinstall.  It is not uncommon that a clean rebuild and reinstallation
> is the solution to mystifying problems.
>
> Eric
>
>
Looks like you are right.  A complete clean-out and rebuild fixes the
problem.  I might have messed something up a while back when testing some
clipping issues.

Thanks,
Ben Root

On 07/22/2010 04:34 PM, Benjamin Root wrote:
> Heh, looks more pervasive than just the Tkinter backend, and it isn't
> just caused by zooming.  Just moving the image off to the side is
> enough, and saving that figure using the "Save" button produces this
> attached image.
>
> And further testing shows that this occurs if I manually set my limits
> before the .show() call and save using .savefig()
>
> Attached is a simple script.

Running your script, I don't see any artifacts with gtkagg or with 
tkagg, or if I save the file to png.  I'm also running with latest svn.

I wonder whether your installation has gotten scrambled?  You might try 
deleting your build directory and your installed mpl, then rebuild and 
reinstall.  It is not uncommon that a clean rebuild and reinstallation 
is the solution to mystifying problems.

Eric

>
> Ben
>
> On Thu, Jul 22, 2010 at 9:14 PM, Benjamin Root <ben...@ou...
> <mailto:ben...@ou...>> wrote:
>
>     Attached is a screenshot of what I am seeing with the Tkinter
>     backend (I haven't tested others).  The lines aren't getting plotted
>     outside the zoomed-in region, but the markers are.  I don't recall
>     this happening before, but I can't be 100% sure of that.
>
>     I am using the latest mpl from SVN.
>
>     Ben Root
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Heh, looks more pervasive than just the Tkinter backend, and it isn't just
caused by zooming.  Just moving the image off to the side is enough, and
saving that figure using the "Save" button produces this attached image.

And further testing shows that this occurs if I manually set my limits
before the .show() call and save using .savefig()

Attached is a simple script.

Ben

On Thu, Jul 22, 2010 at 9:14 PM, Benjamin Root <ben...@ou...> wrote:

> Attached is a screenshot of what I am seeing with the Tkinter backend (I
> haven't tested others).  The lines aren't getting plotted outside the
> zoomed-in region, but the markers are.  I don't recall this happening
> before, but I can't be 100% sure of that.
>
> I am using the latest mpl from SVN.
>
> Ben Root
>