Hi, After switching over from the MacOSX backend to the GTKAgg backend, I started notice a big change in drawing behavior.
Now I know that MacOSX is interactive all the time by [mis]design, so I wasn't surprised that I would have to add draw() commands when isinteractive()==False; however, when using the non-pyplot commands, i.e. ax.plot() rather than plot(), I must use draw() to render the new Line2D even when isinteractive()==True. This doesn't seem correct behavior to me. A lot of drawing just can't be done by the pyplot functions. You have to go to the axes functions. On another, but related topic, I use ipython -pylab, and generally develop by using the `run -i file.py` syntax. I have found what I think is a bug where if I have a file that consists of: cat >> file.py <<EOF print isinteractive() EOF and I do In [1]: isinteractive() Out[1]: True In [2]: run -i file.py False which means I either have to do ion() or draw() each time even for pyplot commands. Is this a bug in ipython or matplotlib? M ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
