Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!venera.isi.edu!raveling
From: raveling@isi.edu (Paul Raveling)
Newsgroups: comp.sys.hp
Subject: Re: X11R4 Transparencies
Message-ID: <12150@venera.isi.edu>
Date: 2 Mar 90 21:04:04 GMT
References: <9817@batcomputer.tn.cornell.edu>
Sender: news@venera.isi.edu
Reply-To: raveling@isi.edu (Paul Raveling)
Distribution: comp
Organization: USC Information Sciences Institute
Lines: 39

In article <9817@batcomputer.tn.cornell.edu>,
gdykes@batcomputer.tn.cornell.edu (Gene Dykes) writes:
> 
> 			xterm -bg Transparent
> 
> This used to work in X11R3.
> Under X11R4 it still works for Turbo SRX, but not for SRX.
> 
> Apparently, XAllocNamedColor returns a black pixel for "transparent".

	I believe the correct definition of transparent was RGB = (1 1 1),
	which looks like black.  If the call fails though you'll probably
	wind up using true black as a default.

> Is this my problem, X11R4 problem, or HP server problem?
> Is there a fix for this?

	If you're using the MIT standard color name database,
	it doesn't include "transparent".  MIT takes the position
	that it's inappropriate to supply "transparent" for everyone,
	since the variant HP uses either (a) doesn't apply or
	(b) may conflict with usage by other vendors.

	To supply this in the X11R4 color database, edit
	$(TOP)/mit/rgb/rgb.txt to include a line looking roughly like:

1 1 1		transparent

	Then do a "make" and a "make install" in that directory.


	That'll assure that you have "transparent" defined.  I have
	no idea though whether there may be other problems involving
	the display server's interpretation of it.


----------------
Paul Raveling
Raveling@isi.edu