Re: "raise" for raise gnuplot console too?

[Ethan M. <merritt@u.washington.edu>]

On Wednesday 06 June 2007 15:32, Daniel J Sebald wrote:
> would it make sense to have a command that raises the console? 
> > 
> > No.
> > That is the job of your window manager.  You can't even type the command
> > unless you have focus, and if you have focus you can hit whatever key
> > your window manager likes to use for this purpose.  It would be absurd to
> > argue that every application should implement this basic window management
> > function all over again, probably inconsistently with N other apps.
> 
> You may have a setup that works fine, but my point is that I've never had a 
> configuration (I use gnome, not kde) that gets away from requiring the mouse 
> click in some way as opposed to just staying with the keyboard.

Depends on the window manager. Gnome has a well-deserved reputation for
making it hard to change the default behaviour of anything, but if you
can't even change the focus policy that would be beyond absurd.
A quick Google search suggests it is actually quite easy:

Sawfish:
    Helix GNOME Control Center
	The selection box at the top determines how the mouse pointer sets focus.
	The default is to focus when the mouse clicks on the window. The other 
	choices are to focus only when the pointer is in the window ("enter-exit")
	and focus stays with the last window entered ("enter-only").

Enlightenment:
    Enlightenment configuration tool
	Keyboard focus follows
	These buttons determine how "focus" is selected by the actions of the mouse.
	The available settings are Mouse Pointer (focus follows mouse),
	Sloppy Pointer (focus follows mouse after a delay), and Pointer Clicks
	(focus is given to window on which a mouse clicks).

 
> My idea would be simply to do:
> 
>      term = set_term(c_token);
>      [snip]
>      if ({term INTERACTIVE OR HAS MOUSE SOMEHOW})
> 	guiterm = term;
> 
> and then for raise/lower and event input use 'guiterm' pointer rather than 
> 'term' pointer.

That doesn't work at all.  See previous frustrating discussion in which
I totally failed to explain why.  The core gnuplot code will never even
see the <space> keypress event, so it never has the opportunity to decide
what terminal function to call.  The difficulty is all on the input end,
not the output end.


-- 
Ethan A Merritt