matplotlib-devel Mailing List for matplotlib

I am trying to build matplotlib on Solaris and am getting the following
compile error.  Does this look familiar to anyone?

thanks,
S

In file included from
/work/local-b/sparc-sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/../../../../include/c++/3.4.2/bits/postypes.h:4\
6,
                 from
/work/local-b/sparc-sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/../../../../include/c++/3.4.2/iosfwd:50,
                 from
/work/local-b/sparc-sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/../../../../include/c++/3.4.2/ios:44,
                 from
/work/local-b/sparc-sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/../../../../include/c++/3.4.2/ostream:45,
                 from
/work/local-b/sparc-sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/../../../../include/c++/3.4.2/iostream:45,
                 from swig/agg_buffer.h:7,
                 from src/agg.cxx:1582:
/work/local-b/sparc-sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/../../../../include/c++/3.4.2/cwchar:145:
error: `::btowc' has not been declared



		
__________________________________ 
Yahoo! Mail for Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail 

I wrote once before
(http://sourceforge.net/mailarchive/message.php?msg_id=12093643) about
some new methods for animation that can enable fast animations in
matplotlib, which can support everything from dynamically updating
your data to strip charts to real time cursoring to a widget like
canvas.

So far, only GTKAgg has complete support for the required methods.  I
think it would be nice to have these in the major mpl GUI backends,
since it would make the animation interface much simpler and cleaner
if we could rely on them in the frontend, eg in the Axes class.

I just posted an entry on the wiki about matplotlib animations.  It
starts with regular "pylab" animations, and then discusses GUI
animations using timers and event handlers, and finally the newfangled
methods to support per-artist animations.

As it turns out, for the *Agg backends, only one new method needs to
be added, which is 

  canvas.blit(bbox)

This method transfers the agg canvas within the bounding box onto the
GUI canvas.  I realize that I need to add something like 

  aggcanvas.as_rgba_str(bbox) 

to support this for Qt and WX which are currently using string methods
to blit to canvas.  I'm happy to do this in the next couple of days if
I know that someone is interested in actually implementing
canvas.blit(bbox) for their respective backend.

To see the utility of the new methods, run examples/widgets/cursor.py
and examples/widgets/span_selector.py modified to set useblit=True,
and compare the performance of anim.py with examples/animation_blit.py
which animate the same data.  All of the above should be run done with
the GTKAgg backend.

As noted on the wiki entry, with these methods in place, users who
want to do per artist animation could write code like

    line, = ax.plot(something, animated=True)
    canvas.draw()   

    def callback(*args):
        line.set_ydata(somedata)
        ax.draw_animated()


This *doesn't* work now, because I am hesitant to put methods into
Axes which would break most backends.  The equivalent in
animation_blit.py is considerably more complicated.

Perhaps someone at STScI could sign up for implementing
canvas.blit(bbox) for TkAgg, and someone at JPL for the Qt backend?  I
might take a crack at WX, if noone else wants it :-) Steve, Gregory
and Charles, if you are interested in animation for your respective
backends, I encourage you to take a look at this too.  Those of you
using the agg buffer in extension code (eg tkagg) may want to look at
src/_gtkagg.cpp to see how the bbox and the agg buffer are used to
implement blit, which defaults to blitting the entire canvas if
blit=None.  
All of this is discussed in more depth at
http://www.scipy.org/wikis/topical_software/Animations

Thanks!
JDH

On Mon, 2005-08-01 at 20:26 -0700,
mat...@li... wrote:
>         
>         In some cases, there appears to be a bug in SVG image
>         handling.  For
>         example, the image in the colorbar is not properly sized
>         
>             import pylab as p
>             p.imshow(p.rand(5,3))
>             p.colorbar()
>             p.savefig('test.svg')g
>             p.show()
>         
>         This problem appeared before and after Steve's application of
>         Norbert's PNG patch (thanks's Norbert!) so it looks like
>         something
>         else is to blame. 

One problem with the colorbar is that the png file "im.write_png
(filename)" creates is upside down, image_demo.py creates an upside down
png too.

I see that the GTK/GDK backend does not use im.write_png() but uses
im.as_str() which has a 'flipud' argument to flip the image.
Is it possible for im.write_png() to take the 'flipud' argument and flip
the image for the SVG backend?

The name im.as_str() is a bit vague - what kind of string? Something
like im.as_rgba_str() would make it a bit clearer.

Steve

Send instant messages to your online friends http://au.messenger.yahoo.com