matplotlib-users Mailing List for matplotlib

>>>>> "Mark" == Mark Engelhardt <ma...@st...> writes:
 Mark> Hi, Two quick little issues I haven't been able to figure
 Mark> out how to fix on my own so far:
 Mark> 1. Is there an easy way to change the spacing between
 Mark> subplots, so that they aren't so crammed together? It's
 Mark> none too pretty when the x-axis text for the upper plot is
 Mark> overlapping or even below the title for the lower plot.
Which backend are you using? Chris Fuller submitted a tk widget for
just this purpose -
http://sourceforge.net/mailarchive/message.php?msg_id=8901913. It
would be fairly easy to port to other GUIs. It's on the list of things
to do, but I haven't had time. Other than that, your best option is
to manually set the axes size, eg using the 'axes' command or calling
 ax.set_position
 Mark> 2. Is there a way to make the 'show()' command execute so
 Mark> that the script keeps running (instead of waiting for the
 Mark> windows to be closed), and to have the output persist past
 Mark> the end of the run?
You should only call show once per script. I repeat, you should only
call show once per script -
http://matplotlib.sourceforge.net/faq.html#SHOW
matplotlib-0.60.2 has a "draw" command to force a canvas redraw. This
is non blocking. Earlier versions allow you to do, equivalently,
get_current_fig_manager().canvas.draw(). Does this do what you want?
I am not sure what you are after when you write "have the output
persist past the end of the run". Launch the python interpreter?
Please let me know what backend you are using and explain a bit more
what it is you are trying to do. Are you running in interactive mode?
JDH

Hi,
Two quick little issues I haven't been able to figure out how to fix on 
my own so far:
1. Is there an easy way to change the spacing between subplots, so 
that they aren't so crammed together? It's none too pretty when the 
x-axis text for the upper plot is overlapping or even below the title 
for the lower plot.
2. Is there a way to make the 'show()' command execute so that the 
script keeps running (instead of waiting for the windows to be closed), 
and to have the output persist past the end of the run?
Thanks,
Mark

One would expect the following will fill up the plot window:
>>> n=zeros(20000)
>>> n[::2]=1
>>> plot(n)
The plot "stops" a little more than half way, as if it "runs out of ink".
It happens on Linux as well as Solaris, using either numarray and Numeric,
and both TkAgg and GTKAgg, but not GTK. Is this due to some AGG limitation?
JC Hsu

 Hi John,
 I'm sending the code as an attachement, as it is 215 lines long
and some of them could wrap. Some thoughts about the code: in order to
test it just modify the definitions of IMAGE_FILE and (maybe)
PRINT_DPI. Then start the program and use "print" and "preview" from
the "file" menu. The preview doesn't look like the original plot (at
least on the machines I tested it), and I don't know why. The colors
seem to be twisted or something in the preview. If somebody has any
clues about this, I'd be more than happy to know. However, this is
only a preview problem, the print itself looks fine. Don't expect the
code to run on the current "official" version of wxPython (2.5.1.5);
download the 2.5.2.2 test release (or a more recent version) from
http://starship.python.net/crew/robind/wxPython/daily/20040722/. Only
tested on WinXP and Win2000 with the WXAgg backend, I don't know
anything about the other platforms or backends, if someone else could
test this it would be great. This could certainly be improved by
telling the backend what wxDC it should use to draw the image on (thus
skipping the save image/load image step), but so far I believe this is
a good solution.
 John, I have some comments on the wx / wxAgg backends; I've been
able to totally eliminate the very annoying flicker that I got when
moving a window on a plot canvas. I guess that the dev list would be a
better place for these comments, right?
-- 
Bogdan