|
From: Hans-Bernhard B. <br...@ph...> - 2003-12-08 16:58:30
|
On Sat, 6 Dec 2003, Petr Mikulik wrote: > 3. It must impact all screen terminals of the currently running gnuplot, > whatever is your currently selected terminal (I want to raise my PM > window even when generating a postscript file -- just to have a look). > Thus, the implementation I did for OS/2 and Windows is correct. > Further, there is no need for a new terminal API (yet) -- that OS, > which wants to support this, just adds its #ifdef. I rather strongly think that there is a need to put this into the terminal API definition. Pause is not as similar as you make it out to be --- that one deals with the command line interface, not with the graphics output. Pause doesn't doesn't belong into the terminal interface, but a prospective new command whose sole effect is to change the state of terminal output (i.e. plot windows), definitely does. > Thus, on any OS, there is no way to find which gnuplot terminal window > belongs to which gnuplot console instance. As I see it, _this_ would be the only real reason that a command from inside gnuplot would be needed. I'm not sure the application running gnuplot through a pipe couldn't just send a GUI event to the window manager or the main gnuplot window to raise the gnuplot window and all of its children, but if that can't be done, then yes, a 'raise' command would be the way to go. -- Hans-Bernhard Broeker (br...@ph...) Even if all the snow were burnt, ashes would remain. |