On Mon, Sep 30, 2002 at 06:05:06PM -0700, Tim Freedom wrote:
> I had mailed about this like a couple of weeks ago, but it doesn't
> look like my mail made it to the mailing-list. In any regard, let
> me broach the subject again. I grabbed an fvwm snapshot (back in 9/16)
> and then again 9/26 and compiled them without a hitch, but the colormap
> is all freaky on me (gotta love that description :-) Simply put,
> without making any changes to any of my setup files, my emacs and icons
> are very different in tone/color. A case in point, the clamp.xpm is
> yellowish in color when it should really be brown. If I invoke 'xv'
> from the command line and look at clamp.xpm, it looks fine (its brownish).
> I don't have any "colormap" commands in my .fvwm2rc file (FWIW).
>
> I'll attach a small example of what I'm talking about. Even the rcalc.xpm
> (also noted in the jpg) instead of having a gray edge has a redish one.
>
> I looked at the Changelog to see any mention of 'colormap' and downloaded
> a few snapshots in between any mention of that word to see where the
> problem started happening for me; here's a summary,
>
> + snap-20020926: exhibits the same problem (colors look wrong)
> + snap-20020916: exhibits the same problem (colors look wrong)
> + snap-20020904: exhibits the same problem (colors look wrong)
> + snap-20020831: exhibits the same problem (colors look wrong)
> + snap-20020815: exhibits the same problem (colors look wrong)
> + snap-20020810: exhibits problems, different form (more faded)
> + snap-20020805: exhibits problems, faded + FvwmPager is green-puke color
> + snap-20020731: exhibits problems, faded + FvwmPager is green-puke color
> + snap-20020720: exhibits problems, faded + FvwmPager is green-puke color
> + snap-20020715: Works great
> + snap-20020501: Works great
>
> So it might be this change that is causing the problem,
>
> --
> 2002-07-18 olicha <olivier.chapuis_at_fr...>
>
> * libs/PictureUtils.c (PictureRGBtoPixel):
> (decompose_mask):
> Fixed(??) color allocation for some visuals
> --
>
Not exactly I think. In what follow I assume that you have a screen
which supports only 256 colors (8 bit depth). Can you confirm this?
The point is that a new color limit method has been implemented for
such a screen. New colors tables are used so that it is possible to
use gradient in such screens (and use bg pixmap with a lot of close
colors in Colorset). One pb with these new tables is that they have
not enough grey (so the pb with the calc icon). This may be fixed in
the future. Also colors approximation formulae has changed and I am not
sure that the new one are so good. But remember that with a 8 bit depth
screen fvwm will never use true colors for icons but colors in a table
(and any reasonable app will do the same things with such screens, if
it has to display a lot of colors).
You can still use the "old" table by using the following option
-color-limit 61. Moreover, when the "old" table was build I think that
the (IMHO ugly, do you try wm-icons package :o) icons you use was used
for testing. Unfortunately, you can still have "pbs" because colors
approx was done in a different way (BTW, in two steps one by fvwm and
the other by the xpm lib).
You may alos try to use dithering: use Colorset in your FvwmButtons:
Colorset 10 bg grey, fg white, ditherIcon
*FvwmButtons: Colorset 10
# remove the Back and Fore colors option
# ... your config
and start fvwm without the "-color-limit" option
(DitherIcon/NoDitherIcon are not dynamic, you should restart the
Buttons after a change). BTW, ditherIcon is an undocumented Colorset
option because maybe it will be removed. Also, there are not enough
doc about the -color-limit option as the code is not finished.
You may also try to start fvwm with -color-limit 125 or 216.
But you will probably have pbs with certain apps you use
(or fix some pbs with some gtk apps).
Any feedback is really welcome.
Regards, Olivier
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Oct 01 2002 - 01:52:18 BST