Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!SABER.COM!jimf
From: jimf@SABER.COM
Newsgroups: comp.windows.x
Subject: Re: xloadimage -onroot
Message-ID: <9010041412.AA02689@armory>
Date: 4 Oct 90 14:12:23 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 28

|When I do an xloadimage -onroot, how do I later free and get rid of
|the pixmap on the root window?

The pixmap will be freed automatically when you load another one.  I'm
not sure if it gets freed if you set the background pixel, perhaps one
of the server internals people would know.

|I noticed xloadimage does an
|   XSetCloseDownMode(dpy, RetainPermanent);
|so that the pixmap will not be freed when it exits.
|
|It also puts a property on the root window with the pixmap id.
|"xprop -root" returns:
|   XA_XLOADIMAGE_COLORS_XID(PIXMAP): pixmap id # 0x1500003
|
|If I do an "xkill -id 0x1500003", will that free the pixmap?

It will free the colormap; the pixmap used for the property is a dummy
placeholder.  Doing this might confuse future runs of xloadimage
because the property will still be around although the ID will be
invalid.

The next patchlevel of xloadimage will address these problems, thanks
for bringing them up.

jim frost
saber software
jimf@saber.com