On Sun, Sep 08, 2002 at 10:02:04AM -0400, Dan Espen wrote: > Olivier Chapuis <[EMAIL PROTECTED]> writes: > > On Sun, Aug 11, 2002 at 11:48:19PM +0200, Olivier Chapuis wrote: > > Ok, so I suggest this: > > - By default here (no already pre-allocated), use a non preallocated static > > table. And even: > > - Never free colors allocated in the table, but always free colors > > allocated outside. This is a bit "weak" but this seems reasonable > > for me as restart can free the colors (sic) and 8 depth users without > > the XRender extension may use simple colors config. > > > > Dan? > > The more you can do to limit color use by FVWM the better. > Using a restart doesn't seem good. >
Yes, but I am not sure we win a lot by freeing the colors allocated in the table. On the other hand this may take a lot of memory or make the loading of certain image/gradient slow. Ok, I will not remove the possibility to free colors in the table and fixes these "weak" colors leaks when possible at feature freeze time. > I'm concerned about how complicated this has become. > I haven't figured out how a user would figure out which > options to use. Yes there is more configuration possibility. But there are a lot of situation we have to deal with as the good option depends on the applications the user use. fvwm can now share its colors with XRender, qt and gtk (this is where a lot of colors may be a good things). Moreover, this is done automatically when possible (auto detection of "pre-allocated" table). Also, an interesting new possibility is that color limit can be applied to _all_ the colors used by fvwm (some effort may be done on the sh/hi colors in the future). So the situation is as before: 1. do nothing, 2. If you get problem try to limit the colors (and for gtk pbs try to ask fvwm to pre-allocate a lot of colors!). > I know you haven't finished the documentation yet. > I will try to wrote a clear doc. 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]
