On 09 Jul 2002 08:18:33 +0200, Olivier Chapuis wrote:
>
> We can add a new cmd
>
> EffectSet 123 fg blue 30, bg red 50, PixmapTint black 10, IconTint black 10, \
> fg_text 80
>
> The advantage is that one EffectSet can be used for multiple colorset. The
> disadvantage come from updating problems: at "startup" there is no pbs,
> you define EffectSet 123 and after colorset 234 which use Effect 123 when
> the main colorset pixmap is created. But now if you want to change
> the pixmap of the colorset 234 and its tint you should do
>
> Effectset 123 PixmapTint white 10 # -> we should update the main pixmap of
> colorset 123 (and maybe others) and
> send it to the modules
> Colorset 234 Pixmap New.xpm # -> update and send again ...
>
> So it seems we should have two "EffectSet" command: EffectSet (just the
> definition of the tints and alpha's) and EffectSetAndUpdate (tint/alpha
> def + update all the colorset which use the tint set).
I think an effect (tint, alpha) should be only a filter, that only affects
(until disabled) the corresponding properties, and does not change them.
In the future we may add something like DissolveEffect that transfers an
effect to a colorset permanently, but this is not important for now.
But I don't think Effectset is really needed,
> IMHO, I think that just having bgTint, fgTint, shTint, hiTint,
> PixmapTint and IconTint _into_ the Colorset command is a simple
> and good solution. So if there is no "strong" vote for EffectSet
> and EffectSetAndUpdate I will implement tinting this way.
Agree, so Effectset may be emulated using a function.
AddToFunc ApplyColorsetEffect
+ I Colorset $0 fgTint blue 30, bgTint red 50, IconTint black 10, ...
AddToFunc ResetColorsetEffect
+ I Colorset $0 *Tint, *Alpha
The last 2 special names with asterisk are shortcuts, they may be used to
set the same tint or alpha effect parameters to all relevant properties,
or to reset them.
I think that properties <property>Tint and <property>Alpha should be reset
automatically when <property> is changed, either directly or inderectly.
I am not sure what hiTint and shTint are good for. They should use bgTing.
> In addition of tint I would like to implement user defined alpha-blending
> and Add*Pixmap. We already have fg_alpha (maybe this should be fgAlpha),
> and I would like to have:
>
> PixmapAlpha percent # apply the pixmap with a fading effect
> # determined by percent
> IconAlpha percent # the same thing for the contextual (mini-)icon
>
> Finally I think it will be good to be able to add _one_ pixmap:
>
> Extra{,Tiled,Aspect}Pixmap image_file
>
> (together with ExtraPixmapTint and ExtraPixmapAlpha)
>
> Mikhael suggests to use Alpha*Pixmap in the place of Extra*Pixmap,
> but I think that "Alpha" will be confusing. Also Mikhael
> suggests to use an other syntax by using "Image" in the place
> of "Pixmap" everywhere. I am not sure we should change the
> syntax (even with back compatibility).
We already changed the colorset syntax by removing FvwmTheme.
I suggest to use the word Image for the same reason that we once renamed
PixmapPath to ImagePath, now fvwm even supports xbm and png, not just xpm.
I think you agree that 3 existing properties (TiledPixmap, AspectPixmap
and Pixmap) are not really 3 but 1, every one disables an other.
And you suggest to have one PixmapAlpha, not separate alphas for all 3.
So instead of duplicating these properties to ExtraPixmap and having 6,
I suggest to have only 2 properties:
Image and SecondImage (or ExtraImage)
And accordingly:
ImageAlpha and SecondImageAlpha
> So, may I go?
I would say, yes, after we come to an agreement about names. :)
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]
