Re: FVWM: FvwmCascade and FvwmTile betas Released

From: Nick Cross <rnc_at_prismtech.co.uk>
Date: Wed, 27 Nov 1996 15:38:23 +0000

lar3ry gensch wrote:
>
> Andrew Veliath wrote:
> >
> > I've just put new versions of both of my new modules, FvwmCascade and
> > FvwmTile on my modules page. Of course, the new member is FvwmTile
> > which lets you tile windows in all sorts of ways. FvwmCascade also
> > has a new option to force windows to resize to a certain height. Both
> > of these modules are sort of complementary.
>
> These modules are pretty nice, and they work nicely with fvwm95-2.0.42a
> as well as fvwm2.0.43 (just to let you know).
> One comment that I can see coming up is that maybe have some support for
> a tile or cascade 'region' -- for instance, many fvwm95 users have a
> task bar on the screen that can get obscured by these modules. In
> addition, there are lots of people with button bars, pagers, and whatnot
> that they don't want obscured.
>
> I was thinking that a simple solution would be to add some new
> parameters:
>
> *FvwmCascadeRegion 0 20 1280 1004
> *FvwmTileRegion 0 20 1280 1004
>
> This would limit the region in which the windows are placed to the
> rectangle defined by the corners (0,20) and (1280,1004), leaving the 20
> pixels from the top and 20 pixels from the bottom clear of any added
> windows (assuming a 1280x1024 screen size).
>

But, I believe this is already implemented. The way I have it is
+ "&Tile" Module FvwmTile -u -mn 2 -m 0 0 97 97
in one of my menus which tiles the windows from 0,0 to 97,97 percent of
screen size - quoting from the manual -
Up to four numbers can be placed on the command line that are not
switches. The first pair specify an x and y offset to start the first
window (default is 0, 0). The second pair specify an absolute
coordinate reference denoting the lower right bounding box for tiling.
If any number is suffixed with the letter p, then it is taken to be a
pixel value, otherwise it is interpreted as a screen percentage.


> The other possible solution (which I think would be more difficult) is
> to determine where StaysOnTop windows appear on the screen and avoid
> those areas, sort of the way the CleverPlacement code works.

Testing it out it already ignores sticky windows which are stays on top.
What I would really like however is to be able to specify tile the
windows in a maxtrix format but with a *minimum* size....any chance?


Nick
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Wed Nov 27 1996 - 09:37:19 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:59 BST