On Thu, Sep 13, 2001 at 03:29:20PM +0700, Dmitry Yu. Bolkhovityanov wrote: > Hi! > > First, a pair of questions regarding window decorations. > > 1. Is it possible to make titlebar buttons appear not side by side > to each other and to borders, but at some offset? So that it would be > possible to make a setup similar to OpenWindows (where the "window ops" > button is at some distance from the left) and to MacOS/Aqua-alikes (where > buttons are disjoint)?
Its not possible with vector buttons but can be done with pixmap buttons. The following lines come from the system.fvwm2rc-sample-95: ButtonStyle 1 MiniIcon (-- flat) ButtonStyle all -- UseTitleStyle Flat AddButtonStyle 2 Pixmap mini.winXX-close.xpm AddButtonStyle 4 Pixmap mini.winXX-maximize.xpm AddButtonStyle 6 Pixmap mini.winXX-minimize.xpm Just give the pixmaps a transparent border in the dimensions you like. Unfortunatey you'll have to draw a separate pixmap for each button state if you need depressed and toggled looks. > 2. Somewhere after 2.2.4, the decoration code was changed so that > borders became wider. This had several visible effects, all of which are > IMHO negative: > > a) windows occupy more space (with 2.2.4 on 1152x864 > screen xterm with lucidatypewriter-12 font could be > tall-maximized to occupy exactly full screen with 64 > lines, and xterm with lucidatypewriter-10 could be > wide-maximized to use exactly full screen width; now > there are unused gaps); The size of the decorations *didn't* change internally in fvwm. If things don't fit nicely anymore then either the font in your xterms has changed or fvwm's title font (TitleFont foo) or the width of the window borders (HandleWidth and BorderWidth styles). > b) hilited parts of titlebar buttons stick -- see topmost > scanline of buttons ##0,8. I'm not sure what you mean. Can you perhaps just provide a screenshot? > The question is -- can this be fixed, or, can somebody please > point me to appropriate place in list archives where this change is > discussed? > > Second, Dominik, can bug #732 have a simple "fix" -- since this > effect isn't so fatal with non-animated shading, maybe add something like > if (border_width == 0 && has_no_title) steps = 1 > to CMD_WindowShade()? I'll take a look. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
