On Fri, Sep 20, 2002 at 01:01:52AM +0000, Mikhael Goikhman wrote:
> On 19 Sep 2002 15:48:19 +0200, Olivier Chapuis wrote:
> > 
> > On Wed, Sep 18, 2002 at 09:25:53PM +0000, Mikhael Goikhman wrote:
> > > On 18 Sep 2002 23:01:29 +0200, Olivier Chapuis wrote:
> > > > 
> > > > On Wed, Sep 18, 2002 at 04:25:44PM +0000, Mikhael Goikhman wrote:
> > > > > 
> > > > > Something is wrong with Tint after this commit.
> > > > > 
> > > > > Without any config do:
> > > > > 
> > > > >   Colorset 5 fg white, bg average, TiledPixmap any-image
> > > > >   MenuStyle * MenuColorset 5
> > > > > 
> > > > > Menu looks ok. Now:
> > > > > 
> > > > >   Colorset 5 fg white, bg average, TiledPixmap any-image, Tint yellow 
> > > > > 30
> > > > > 
> > > > > Menu looks flat. Execute the first line without Tint, it is flat
> > > > > forever. This behaviour "Tint makes a colorset flat forever" is
> > > > > not just in menus.
> > > > 
> > > > So hi == sh? I cannot reproduce this (used fvwm-flying.xpm).
> > > > Is this "average" specific?
> > > 
> > > bg, hi and sh are just fine, but the colorset is Plain after Tint.
> > 
> > Ok, no problems at all here :o/
> > I've made some very small clean up in colorset.c and FRender.c just now,
> > but I do not think that this fix something for you.
> > I suspect a XRender pbs.
> > Can you go at line 998 of libs/PictureGraphics.c and add a 0 &&
> > just before FRenderRender. Then, try again ...
> 
> Yes, it works as expected when I comment this if.
> 
> I am sending you the output of `xdpyinfo -ext RENDER`;
>

The output seems normal for me (in accord with the XRender protocol :o).
Can you try the new code? I do not think it will fix the problem ...
Any way, if it fix the pb can you uncomment the line

/* #define USE_ABSOLUTE_FORMAT 1*/

in the beginning of libs/FRender.c and try again (do not do
that if the pb does not go away).

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]

Reply via email to