Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!jade!violet.berkeley.edu!jkh
From: jkh@violet.berkeley.edu (Jordan K. Hubbard)
Newsgroups: comp.windows.x
Subject: Re: bitmaps and backgrounds
Message-ID: <5553@jade.BERKELEY.EDU>
Date: Wed, 21-Oct-87 12:41:06 EDT
Article-I.D.: jade.5553
Posted: Wed Oct 21 12:41:06 1987
Date-Received: Sat, 24-Oct-87 05:44:56 EDT
References: <885@godot.radonc.unc.edu>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: jkh@violet.berkeley.edu (Jordan K. Hubbard)
Organization: University of California, Berkeley
Lines: 18
Keywords: sigh

In article <885@godot.radonc.unc.edu> sherouse@godot.radonc.unc.edu (George W. Sherouse) writes:
|
|In my fix to XMenu I used a loop over planes to XCopyPlane from the
|bitmap to the pixmap.  I am still not convinced that that is the best
|way to expand a bitmap, but that aside it seems clear to me that a new
|function or macro is needed to prevent ongoing transportability
|problems.  I would propose either XSetWindowBackgroundBitmap
|(functionally identical to XSetWindowBackgroundPixmap but taking a
|bitmap as an argument and expanding it internally) and/or
|XMakePixmapFromBitmap (to standardize the expansion technique) be
|added to Xlib.  The documentation of XSetWindowBackgroundPixmap should

Am I missing something? I thought that bitmaps finally went away in
V11 (I haven't used them yet, so I haven't gotten to that section of
the manual) and were replaced by depth 1 pixmaps. If this isn't the case,
why? I liked the idea of only one data type.

					Jordan Hubbard