matplotlib-devel Mailing List for matplotlib

Sorry about the delay in getting back to you
(I was away for a long weekend and just got
back in today).
On Nov 19, 2005, at 8:22 AM, John Hunter wrote:
> daishi> This patch allows one to use matplotlib with (just) the
> daishi> new scipy.
>
> Just for clarification, when you say "just" the new scipy, you mean
> that it works with Numeric, numarray *and* the new scipy, not that it
> works with the new scipy and only the new scipy.
The intent was so that current users of numeric/numarray
wouldn't see any difference at all, but that matplotlib
would build against the new scipy - I believe this is the
case, mod Fernando's fix.
> In the near term, this means that mpl would compile three
> shared object files for each of the three array objects for each
> extension module, which of course will increase compile times and
> binary distribution sizes.
As it currently stands, the patch will build at most *two*
shared objects, because the build logic is basically:
if numarray:
	# numarray build
if (numeric or scipy):
	# numeric or scipy build,
	# with numeric taking precedence.
It shouldn't be difficult to flatten this out to build
three libraries, however. I submitted the patch in its
preliminary form to see whether there was interest in
going this route at all, since I saw the discussion
about the unified/new array interface plan.
Fernando wrote:
> Minor fix needed to avoid unpleasant surprises for users who have the 
> old scipy on their import path:
>
> try:
> import scipy
> if hasattr(scipy,'__core_version__'):
> NUMERIX.append('scipy')
> except ImportError:
> pass
>
> You want to make sure that you only do this for users of the _new_ 
> scipy, not the old one.
Thanks and sorry about that, this problem
occurred to me over the weekend too.
d

Arg! One petty thing after another. Here is a simple script
demonstrating that the last row does not render the SpanSelector, yet
the callback works fine???
------------------------------------
import matplotlib
from matplotlib.widgets import SpanSelector
matplotlib.use('TkAgg')
from pylab import *
s =3D 3
axs =3D [subplot(s,s,i) for i in xrange(1,s**2+1)]
def onselect(x, y): print x, y
[SpanSelector(a, onselect, 'vertical', useblit=3DTrue) for a in axs]
show()
------------------------------------
Any clues as to where to look for this bug? Sorry to be a hassle, but
I need this specifically to embed in a Tk only app.
Thanks,
 Charlie
On 11/19/05, John Hunter <jdh...@ac...> wrote:
> >>>>> "Charlie" =3D=3D Charlie Moad <cw...@gm...> writes:
>
> Charlie> Awesome, thanks! Out of curiousity... did you figure
> Charlie> this out visually or by comparing with something?
>
> Let's just say I've encountered the flipy bug before :-)
>
> JDH
>

I'm very interested to see how stuff looks on a Mac. I don't have
access to one, so I'll be looking forward to your results.
I still haven't figured out how to get antialiased lines in EMFs, so
the output doesn't look as good on the screen as all the agg
rendering. But, if you push the dots per inch high enough in the
savefig() command, it looks decent. It does have the advantage of
being a vector format, at least, so it resizes well. :)
It's really worked well for me to be able to embed multiple EMFs and
text and tables in an RTF, with everything machine generated by
Python. Hopefully it works across platforms for you guys.
Rob
On 11/21/05, Ted Drain <ted...@jp...> wrote:
> Rob,
> I think you may have just implemented/discovered/unearthed the Holy
> Grail! This looks fantastic. We have been fighting with EPS files for
> years and trying to come up with a way to have plots that can be embedded
> in Office documents that look good on the screen for presentations and
> still print well.
>
> The EPS preview image has never worked very well and the resulting files
> almost always had problems when moved from MS Office on the PC to/from th=
e
> Mac. If your system works well across platforms, that could save the
> engineers here a lot of time.
>
> We'll have to download this and give it a try. Thanks!
> Ted
>
> At 06:03 PM 11/19/2005, Rob McMullen wrote:
> >I just submitted a patch to add a new non-interactive backend that
> >produces enhanced metafiles, an OpenOffice and Microsoft Windows
> >scalable graphics format that can also be embedded in .rtf files.
> >
> >http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1361839&gro=
up_id=3D80706&atid=3D560722
> >
> >The backend is based on my pyemf package that I finally released with
> >its first public beta:
> >
> >http://pyemf.sourceforge.net
> >
> >The API should be stable -- I'm only planning on adding to it and not
> >changing any existing method signatures in the version 2.0.* series.
> >
> >Oh, and I didn't say so in the patch itself, but I'm happy to donate
> >the patch to matplotlib under the default matplotlib license.
> >
> >Rob
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
> >Register for a JBoss Training Course. Free Certification Exam
> >for All Training Attendees Through End of 2005. For more info visit:
> >http://ads.osdn.com/?ad_idv28&alloc_id845&opclick
> >_______________________________________________
> >Matplotlib-devel mailing list
> >Mat...@li...
> >https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
> Ted Drain Jet Propulsion Laboratory ted...@jp...
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
> Register for a JBoss Training Course. Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>