Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!ucsdhub!hp-sdd!hplabs!hp-pcd!hpcvlx!steve From: steve@hpcvlx.HP.COM (Steve Hiebert) Newsgroups: comp.sys.hp Subject: Re: xseethru Message-ID: <101950031@hpcvlx.HP.COM> Date: 17 Apr 89 21:56:25 GMT References: Organization: Hewlett-Packard Co., Corvallis, OR, USA Lines: 26 What OS level are you at? Mixing X and Starbase calls to the same device isn't supported before 3.1. (The overlay and image planes are considered two devices unless one is running in Combined Mode in 3.1). If you're running 3.1, you shouldn't be making Starbase calls directly to the overlay planes hardware when X is running there. You should be going to a window. When X wakes up it restores the transparency registers to the values it thinks they should have; modifying the hardware directly doesn't give X a chance to know that something has changed. The SRX and TSRX don't really have a transparent color - we "borrowed" a color (0,0,1) that would normally be a blue so close to black as to be indistinguishable and therefore probably useless. Whenever the server gets a pixel value of (0,0,1) it sets the the overlays to black and the image planes to dominant thereby making the overlays transparent (they actually blend). How about setting "-bg transparent" in your call to xwcreate()? I often do an "xsetroot -solid transparent". It makes the windows in the overlays appear to float over the image planes. It seems more intuitive to me than to have to punch a hole in the overlay planes to get to the image planes. Steve Hiebert Hewlett-Packard Corvallis Workstation Operation