On Mon, Jan 21, 2002 at 03:07:55PM +0100, Olivier Chapuis wrote: > Hello, > > I hope that the Transparent colorset for top level background > work fine now for all modules but for FvwmWharf (a lot of > changes is needed here and there is FvwmButtons if one want > transparency). > > Of course so that Transparency works the module must have the > ParentalRelativity Style. I think it will be good that if > a module has a Transparent colorset background then fvwm2 > sets automatically this style to the module and unset this > style if the colorset is no more transparent (the > WindowShadeShrinks style may be toggled too). This is more > in the spirit of FvwmThemes than using a Style command > after a colorset change. > One solution is to add an FVWM extension to the wm-spec: > we can add a new state FVWM_NET_WM_STATE_PARENT_RELATIVE. > Monitoring this state will allow to automatically sets > the good styles. Is there any objection for this method?
Wouldn't it be better to keep that functionality inside fvwm for now and not export properties to the world? This could be done with a style: SendToModule FvwmTheme ... Style FvwmButtons ParentRelativeFrameBackground > An other problem is transparent modules swallowed into > a transparent or not FvwmButtons, there are currently > some problems when the colorsets of the FvwmButtons change. > The FVWM_NET_WM_STATE_PARENT_RELATIVE properties may help > here too for fvwm modules. But I've no precise idea of how > to fix this problem yet. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
