fourdan at xfce.org
Mon Jan 27 19:30:57 CET 2003
Yes, I think you should XKillClient the owner of ESETROOT_PMAP_ID and
remove the property.
Maybe aterm looks for that and cannot retrieve the pixmap (if, let's
say, someone ran xfbd4 just before).
On Mon, 2003-01-27 at 19:27, Jasper Huijsmans wrote:
> On 27 Jan 2003 19:16:14 +0100
> Olivier Fourdan <fourdan at xfce.org> wrote:
> > Jasper,
> > > Anyway, there is a difference between how xfbd and xfdesktop handle
> > > the image: xfbd sets a 2nd property (ESETROOT_PMAP_ID), making a
> > > copy of the pixmap. I'm not sure if I should add this to xfdesktop.
> > > I didn't think it was necessary.
> > It *is* definitely mandatory!
> > The way Esetroot does it is using two properties:
> > http://mail.gnome.org/archives/wm-spec-list/2002-January/msg00006.html
> > In summary:
> > _XROOTPMAP_ID is the pixmap to be displayed. ESETROOT_PMAP_ID is the
> > pixmap to be destroyed, if any. A program that quits after setting the
> > backdrop will set ESETROOT_PMAP_ID, otherwise it won't, so both types
> > of program are supported. So, you should only kill the owner of
> > ESETROOT_PMAP_ID, not _XROOTPMAP_ID in xfdesktop... Just like xfbd
> > did.
> Isn't that exactly what I'm doing? I set the background and the
> _XROOTPMAP_ID property, and since xfdesktop doesn't exit, it shouldn't
> have to set ESETROOT_PMAP_ID, right?
> Or do you mean I should look for ESETROOT_PMAP_ID and destroy it when
> xfdesktop starts?
Olivier Fourdan <fourdan at xfce.org>
More information about the Xfce4-dev