Re: new command: raise

[Petr M. <mi...@ph...>]

> > Would it be possible to configure Gnuplot's compilation so that
> > it can figure out which terminal should be the "interactive" one?

That's clear how do you compile gnuplot.
#ifdef OS2 => PM is interactive
#ifdef X11 => X11 is interactive
#ifdef _Windows => windows is interactive

> That is where I am still confused about Petr's suggested
> "raise" function.  Suppose your gnuplot session has both a
> of pm window active and an X11 window active.  If you type "raise",
> how is it supposed to know which window you are talking about?

With all of them. It will raise all of them -- all are interactive.

> Petr also suggests that the default is to raise all windows at
> the same time. Maybe I am misunderstanding, because I don't
> see why this is useful.  If the windows are obscuring each other
> already, then sending them all a raise command will still result
> in the same amount of overlap.  What have you gained?

No each other already, but other windows are overlaping all or some of them.
I.e. you have running gnuplot or octave with gnuplot windows, now you have a
look to a man page, then to web browser, and you want to see again all your
plots ... so you want to raise all of them. That's what "raise" command
helps to achieve with zero user effort.

Look this way: Origin and similar graph apps have a common "desktop" for all
windows, so raising Origin will raise its desktop with all windows. Nedit
has menu which list all open Nedit editor windows. Most graphical apps have
"Tile" and "Cascade" functions.
  So gnuplot takes the most easiest way to do just "raise" for all of its
windows.

> Now wanting to send a command to one specific window - that I
> understand, although I still think it is more properly a function
> left to the window manager.

Window manager don't let you distinguish which gnuplot graphics window
belongs to which gnuplot console. (*you* would have to explicitly title such
windows *in advance* -- so it is very cumbersome)

---
Petr Mikulik