On Fri, Oct 18, 2002 at 09:02:39PM +0000, Mikhael Goikhman wrote: > On 17 Oct 2002 06:41:05 -0500, FVWM CVS wrote: > > > > Modified files: > > . : ChangeLog NEWS > > fvwm : builtins.c > > libs : Colorset.c > > modules : ChangeLog > > modules/FvwmBacker: FvwmBacker.1 > > > > Log message: > > * My God, Do not BroadcastColorset in CMD_Colorset, parse_colorset do > > that!!! > > * Use a 1x1 pixmap and not a widthxheight pixmap for Plain color in > > CreateBackgroundPixmap > > * A bunch of news (last 4, needs lang check) > > * Documented RetainPixmap FvwmBacker option (needs lang check) > > I think after this commit RootTransparent in menus does not work, > i.e. there is a solid background. Transparent works. > I use fvwm-root to set a background, so this is not a problem. >
This is normal, fvwm-root will have an option -retain-pixmap which allows RootTransparent to work (future patch by Cameron Simpson I hope). At present time you should use Esetroot or FvwmBaker with *FvwmBaker: RetainPixmap. It is absurd that fvwm-root retain the pixmap by default (memory wasting), so fvwm-root just signal that it change the root bg by setting the _XSETROOT_ID property to None (so that the memory safe ParentalRelativity method works). For root transparency the _XROOTPMAP_ID and ESETROOT_ID properties should be used. This is coherent. The ParentalRelativity method use _XSETROOT_ID and the "E" method use _XROOTPMAP_ID and is off by default for memory reason. Olivier -- 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]
