John Hunter-4 wrote: > >> I think that for interactive work such as you describe, ipython -pylab >> pretty well solves the problem, and provides window behavior like >> matlab's. > Yes, exactly. Those of you trying to make this work may want to read > http://matplotlib.sf.net/interactive.html . >
Yes, iPython takes care of these issues in interactive use. I've been trying to stay on mainline Python for portable application development and was using the interactive Matlab scenario as an example of "expected" non-blocking behavior. Interactive use isn't the end-goal for me, or, I think, for Dan. The root issue is the need to keep other activities running while a plot window is open, which comes back to the blocking behavior of show(). It looks like the code linked in the previous post does the job; it just requires getting under the hood of GTK a bit more to use a separate manager function for each plot window. That's fine, and actually it seems it would be preferable as the default behavior of matplotlib (though each backend probaby requires unique code). There are other alternatives: plot to a file and display the image in a window, which loses the zoom/pan functions in matplotlib windows, or launch the matplotlib plot window as a separate process or program. Thanks, Scott -- View this message in context: http://www.nabble.com/threading-problems-tp18015447p18055354.html Sent from the matplotlib - users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
