F. Vhrstrwm writes:
>I have a small whish myself:
>I have the goodstuff buttonbar to the right and it is sticky and ontop.
>I would like the left edge of the bar to behave like the screen border.
>That is, it should block windows crossing it for a short time of mouse
>movement. So it would be just as easy to align windows to the button bar
>as to the screen border since the button bar more or less is the new
>screen border.
Yes! Seconded! It would be very nice to be able to have a button bar
(like, oh, say, tkgoodstuff ;^>) treated as something like a screen
"frame". I don't know exactly the behavior that would be ideal.
Perhaps one could define a rectangular region of the screen as the
"available" region (by default the whole thing), and do what
F. Vhrstrwm suggests with its borders, and try to avoid window
placement there? Or have a window attribute that gives a window
special bullying power.
Is it conceivable to actually treat an "available" region in nearly
all respects as the actual screen is treated now? That is to say, a
button/task bar or the like could occupy a portion of the screen
that's not "on" the desktop itself. There might be a special form of
geometry request (from a module) to request placement in (or
overlapping) the unavailable region. This region should be
changeable, so that the whole screen can be made available (e.g., by a
button-bar's "hide" function).
Mark
-------Trivial, right? Let's see who has it coded by dinnertime.
------- :^)
-------
Mark Crimmins markcrim_at_umich.edu
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Nov 27 1995 - 12:45:15 GMT