| [reply]
[d/l] |
As eserte says, using system with a first parameter of 1 is a way of background launching a task, when you are not interested in capturing the output. The reason why your GUI is freezing up is that the program was servicing the system request, not returning into the Tk event loop, so as not to be able to service any GUI events. If you have this problem inside perl code, you can alleviate the problem by periodically calling $main_window->update - a handy trick when using the debugger on a Tk application.
For the times when you are interested in capturing output, use a piped open, open2 or open3, and Tk::fileevent to set up a callback that can read the captured output, line by line.
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
| [reply]
[d/l]
[select] |
In addition to what has already been mentioned, on linux, we would say you need a "fork-and-exec", not just simply and exec. By the way, the '-persist' option to gnuplot may be the culprit, it keeps the subprocess alive which drives the display.
| [reply] |