bump ..
On Thu, Jul 31, 2008 at 11:02 AM, signal seeker <[EMAIL PROTECTED]>wrote:
> Hi,
>
> I have couple of applications in which I have to generate multiple plots
> interactively using the wx backend and wanted to know the best
> approach to take for this. I did search the list for previous
> discussions on this subject, but the approach to take is still
> unfortunately not 100% clear to me.
>
> The first use case is that I want to be able to "show" plots as soon
> as they are ready. The script sits in a loop pulling out data from
> different sources, does some transformations and then plots it. Now I
> understand the recommended way to call show() when all the plots are
> ready. But since there are many many plots and it take some time to
> generate one, I would like to show the plot window as soon as it is
> ready and furthermore I want all the plot windows to be alive so that
> I can go back and forth through them. I tried using pylab.ion(), but
> then after the script exits, all the windows disappear along with it.
>
> The other use case is more like ipython. I have a program to connect
> to a database and the user interacts with it using queries. I would
> like to add visualization support to it The user should be able to plot
> the data as needed and keep all the plot windows alive.
>
> How can I do this using mpl and wx backend? Do you recommend using
> threading or forking plots as separate processes?
>
> Thanks,
> Suchindra
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
