On Mon, May 26, 2003 at 09:50:26AM +0200, Dominik Vogt wrote:
> On Mon, May 26, 2003 at 09:42:55AM +0200, Olivier Chapuis wrote:
> > On Thu, May 22, 2003 at 10:47:36AM -0600, Sean Seery wrote:
> > > Hello,
> > >
> > > I cannot seem to figure this out so here is my plaintive cry for help:
> > >
> > > How do I get fvwm to support bitmaps with a depth of 24? Every time that I
> > > minimize an application w/such an icon(such as mozilla), fvwm spits out
> > > the following error:
> > >
> > > [FVWM][GetIconBitmap]: <<ERROR>> Window '<some window>' has a bad icon
> > > bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap.
> > >
> >
> > I think I've the solution of the problem (I read all the others mail
> > of this thread).
> >
> > Sean has a 8/24 depth screen and the X server start with DefaultDepth = 8.
> > This is a classical situation (the X server can be configured to start
> > with DefaultDepth = 24, but as certain "old" apps need depth 8 for read-
> > write colours the default is depth 8; moreover on such hardware there is
> > no visual pbs by using certain app under depth 8 and other with depth 24).
> >
> > BTW, since 2.5.6 fvwm detect this situation and fvwm choose to use the
> > best visual: TrueColor depth 24 (before 2.5.6 the user had to use
> > the --visual-id or --visual option; now fvwm need _no_ option).
> > A lot of apps use this logic too.
> >
> > So, for applications supplied icon pixmap we have 3 acceptable depth:
> >
> > - depth 1 (always ok)
> > - depth 8, the default depth
> > - depth 24, the fvwm depth
> >
> > I've just committed a fix.
>
> Cool. Can you backport the fix to 2.4.16 too? It looks fairly
> simple, but I'm not sure I would catch all places I have to touch
> to make the patch myself.
>
Ok. But I do not think I should also backport the autodetection of
the best visual on such hardware. What do you think?
Regrads, 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 Mon May 26 2003 - 05:26:19 BST