|

楼主 |
发表于 2005-2-19 13:07:38
|
显示全部楼层

Config
这个配制原本是在超大屏上使用的...外国就是有米啊 :beat..如果大家想用的话..请参考...
I know that would be a problem. Everything under this bar is unfortunately hardcoded. I got to enhance this topbar with a more flexible resizing option.
Anyway, the topbar's width is 1590 which is a little bit less than my width resolution to make it like it floats in fin air. If you want to keep this behavior, you will have to cut the topbar.png and topbar_shape.xpm of the Arctic's deco to match a size of 1270 = 1280 your screen width - 5 pixels on the left - 5 pixels on the right. Gimp is really the tool to use (I've used it a lot to achieve that kind of things).
Once done, let's have a look to this topbar made of FvwmButtons, shall we. I've defined a geometry for this button of 1590x40+5+5. That's for its size and its placement. So if you keep the 5 pixels space around the topbar, you should end up with something like 1270x40+5+5. As you've noticed, I've set an enormous amount of colums equal to the topbar's width in pixels. This is to achieve placement of swallowed apps at a pixel level. Thus, you should lower this value to match your width: Columns 1270.
Now, it's the turn to the swallowed apps to get resized and moved. The width difference between my desktop and yours is 1600-1280 = 320. So, I advise you to only resize the FvwmIconMan module which size is 1267 in my case. The unfinished VolumeLevel and WifiSensor FvwmScripts have to get moved to the left to avoid their disappearence.
This should lead us to:
Code:
DestroyModuleConfig FvwmTopBar: *
*FvwmTopBar: BoxSize fixed
*FvwmTopBar: Colorset 23
*FvwmTopBar: Columns 1270
*FvwmTopBar: Rows 3
*FvwmTopBar: Geometry 1270x40+5+5
*FvwmTopBar: Frame 0
*FvwmTopBar: Padding 0 0
*FvwmTopBar: ( 125x3+0+1)
*FvwmTopBar: ( 947x1+125+1, Size 947 26, \
Swallow "FvwmIconMan" "FvwmIconMan -g
947x26")
*FvwmTopBar: ( 36x3+1184+0, Size 36 36, \
Swallow "VolumeLevel" `FvwmScript $[fvwm_script]/VolumeLevel \
$[fvwm_theme_img]/volume4.png \
$[fvwm_theme_img]/volume3.png \
$[fvwm_theme_img]/volume2.png \
$[fvwm_theme_img]/volume1.png \
$[fvwm_theme_img]/volume0.png)
*FvwmTopBar: ( 36x3+1226+0, Size 36 36, \
Swallow "WifiSensor" `FvwmScript $[fvwm_script]/WifiSensor \
$[fvwm_theme_img]/wifi4.png \
$[fvwm_theme_img]/wifi3.png \
$[fvwm_theme_img]/wifi2.png \
$[fvwm_theme_img]/wifi1.png \
$[fvwm_theme_img]/wifi0.png)
Just one last thing, this should not bother Fvwm but we never know. The FvwmIvonMan owns also its geometry settings under its configuration file (iconman.fvwm2rc in our case). Thus, it may be adequate to change its value if you run into weird palcement problem. If you need a hand on this, you know where to post Wink |
|