Bill,
The problem is I am writing a bunch of diagonistic tools for users who do
not know anything about unix.
they just want to type a bunch of commands on a shell and see the plots and
they hardly know anything fancy like sending processes to the background :)
I guess, I am going to have to use threads or sub processes to spawn new
plots.
Thanks,
ss
On 6/13/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
On 6/13/07, signal seeker <[EMAIL PROTECTED]> wrote:
>
> Bill,
>
> Thanks for your reply. pylab(ion) is not what I meant. Consider this
simply
> script -
> .....
> # simple.py
> from pylab import *
> plot([1,2,3])
> show()
> ....
>
> Now, if I do python simple.py on a cmd prompt, this will open up a plot
> window, but the script won't return until the plot window is closed.
> I would like simple.py process to end but the plot window to be still
up. I
> have users who would like to type one command after another and not have
to
> close any of the plot windows created.
I see. In that case, I think you just want
$ simple.py &
on unix and
c:\> start python simple.py
on Windows.
In both cases you can put those commands into a script so the user
just types 'run_simple'.
--bb
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
