Richard Curnow
Tue, 17 Dec 2002 02:30:19 -0800
* Mikhael Goikhman <[EMAIL PROTECTED]> [2002-12-16]: > > You don't really need to split a colorset definition to 3 lines, > see enother message in this thread that explains speed problems.
Yes, I saw that message. I was doing it as I was for debugging, so that I could selectively comment and uncomment things to find out what made it work. Now I've cracked it I'm moving to the single line approach. > > > ... but if I uncomment the 3rd Colorset line, I just get white text on > > black menus with no transparency. > > To use RootTransparent use should run "fvwm-root -r bg-image.png|xpm" > first. Or Esetroot. With fvwm-root -r this is now working fine for me. I was using xsetbg before. The manual page says that ought to work, but I suspect I wasn't using a new enough version. > > > I can't get transparent title bars or borders at all though. With title > > bars I'm trying to do > > > > Colorset 1 fg white, bg black, Shape, Plain > > Colorset 1 Transparent > > Colorset 1 tint #4060a0 30 > > TitleStyle Inactive Colorset 1 > > > > but this has no effect and I just get a syntax error reported on the > > console: > > unknown style Colorset : Colorset 1 > > You need 2.5.5 for this. Ok - I've now switched to 2.5.5 and it's basically working as I expected - thanks. > > Only RootTransparent works in titles, not Transparent. > > > Any clues? The syntax for this stuff doesn't seem to be documented much > > yet. > > It is currently fully documented in the FvwmTheme man page that is > referred in the COLORSETS section of the fvwm man page, is not it? Yes, it's there as you say. I was relying on just 'man fvwm' and not finding much. Thanks again. Richard -- Richard \\\ SuperH Core+Debug Architect /// .. At home .. P. /// [EMAIL PROTECTED] /// [EMAIL PROTECTED] Curnow \\\ http://www.superh.com/ /// www.rc0.org.uk Speaking for myself, not on behalf of SuperH -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]