On 13 Oct 2003 00:03:10 +0200, Olivier Chapuis wrote: > > On Sun, Oct 12, 2003 at 03:36:51PM +0300, Mikhael Goikhman wrote: > > I suggest these colorset usability things: > > > > 1) New colorset option "Clear" or "NoEffects" depending on what it does > > that removes all effects from a colorset, it may be aproximately > > equivalent to: > > > > Colorset N NoDither, \ # not sure about this one > > Tint, fgTint, bgTint, Alpha, fgAlpha, IconTint, IconAlpha, \ > > Plain, NoShape, fg, bg # not sure about these 4 > > > > This is intended to be used in dynamical configurations as in: > > > > Colorset N Clear, fg .., bg .., VGradient .. # set completely new colors > > > > I.e. it either resets all effects leaving only fg/bg/image/gradient or > > resets everything. Both are ok for me. Probably reseting everything is > > preferred. In this case Clear may work like CleanupColorsets just on a > > single colorset. > > > > 2) It seems to me that whenever I do "Tint color percent" I always want > > to do "bgTint color percent" too, otherwise the sh/hi colors look > > incorrectly. So I think, "Tint" should also set "bgTint". If someone > > really wants the current behaviour (doubtly), he may always reset > > "bgTint", i.e. "Tint cyan 20, bgTint". For most of cases bgTint will be > > redundant with this proposal. > > What about using fvwm functions > > AddToFunc SetClearColorset > + I Colorset $0 ... clearing ... > + I Colorset $*
This is more or less practical except that it is hard to suggest this to users and they will need this to ensure no previous Tint/Alpha is left. > AddToFunc SetColorsetTint > + I Colorset $0 Tint $1, bgTint $1 This is not practical at all, Tint is always only one of the several options, doing it on a separate line does not help to what I try to achieve, to minimize the syntax for a correct look. > The colorset code is delicate. As we are in feature freeze I am not > very motivated to change some code which seems bug free (for some > minor feature). It is very difficult to argue arguments like these, I don't want bugs myself, but I will try. :) If we will always need to use such SetClearColorset function and never the original Colorset command in fvwm-themes or other setups with dozens of colorsets, then I feel it is not a minor feature, but a misfeature of Colorset command, leading to an unneeded overhead (calling functions). It will also lead to flickering, if it is done using 2 Colorset commands like suggested above. (Yes, it may be done using one Colorset command.) I feel that having different Tint and bgTing is almost always incorrect, we should not default to this. I would like to have both of these things built-in since they seem essential to me (Clear option and making bgTint redundant). > > 3) It seems to me that whenever I do "Transparent" or "RootTransparent" > > I always want to do "bg average" after that. I remember the last time we > > discussed this it was rejected, since it takes time to evaluate average. > > However most of users will need to do it anyway, just explicitely. > > I think "bg average" should be implicetely set after every background > > image/gradient/transparent change. > > > > I think this may be solved nicely in this way. Initially or after "Clear" > > or after "bg average", bg is set to be "average"-ed on every background > > change, hovewer after explicit bg setting, the auto-averaging is off. > > I disagree. "bg average" can be very slow and can use a lot of > (dynamical) memory. It can also reduce fvwm usability under certain > situation, e.g., FvwmBacker big bgs => 2 secs or more for switching > between desks (colorset FvwmBacker bg can solve this but you should > have all your bg in memory ...). I think that it is better that the > user set "bg average" itself (there is a "warning" in the man page, he > takes his responsibility). Having to specify "bg average" explicetely is not very important for me. I just wanted the novice user not to worry about anything when he specifies Colorset Transparent. Currently when someone asks about transparent menus or modules (this happens and will happen all the time), the correct good looking answer is: Colorset 9 RootTransparent, bg average, Tint black 20, bgTint black 20 I hoped, the answer should be (with the same results) just: Colorset 9 RootTransparent, Tint black 20 This is more understandable, the previous line is less intuitive. But again, exlicit "bg average" is not a real problem for me. Regards, Mikhael. -- 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]
