On Mon, 05 Jan 2004 13:28:53 -0500 Dan Espen wrote:
> > Topmost (AcceptsFocus) Focus
> > or maybe Topmost (CurrentPage,AcceptsFocus) Focus
Exactly. That would be nice.
> Are we using topmost in the visual sense?
Not necessarily. I assume FVWM manages a list internally in order to know in
which order to draw windows, e.g. when a screen update happens. A command like
topmost would go through that list, starting from the highest window and
proceed step by step to the lowest window if necessary.
> I think we could do:
>
> Next (!Obscured) Focus
No, that's not what I want. For example, I often have the problem that a
nonfocusable button bar obscures the topmost focusable window. Then I
want that window to be focused (and maybe raised). Here's a little illustration:
+-----------+
|some window|
+-------------+ |
| some window |----------+
+---------------+ | currently|
|Topmost |---+ focused |
+-------+ focusable| | window |
|BUTTONS| window | +------------+
+-------+----------+
Felix
--
To contact me off list don't reply but send mail to
felix DOT klee AT inka DOT de
Otherwise your email to me might get automatically deleted!
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Jan 05 2004 - 16:13:12 GMT