Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ucbvax!xman.sgi.COM!mtoy
From: mtoy@xman.sgi.COM (Michael Toy -- The S.G.I. XMAN)
Newsgroups: comp.windows.x
Subject: GetStaticColormap
Message-ID: <8711030356.AA06098@xman.sgi.com>
Date: Mon, 2-Nov-87 22:56:56 EST
Article-I.D.: xman.8711030356.AA06098
Posted: Mon Nov  2 22:56:56 1987
Date-Received: Sat, 7-Nov-87 00:29:33 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20


In the porting layer document, pg. 25 a function pScreen->GetStaticColormap
is described, however there is no GetStaticColormap function in the screen
structure.  There is a routine in server/ddx/cfb/cfbcmap.c called 
cfbGetStaticColormap, but it is never referenced.

I'm no xpert, but I am wondering what the scoop is here.  As far as I can tell
the correct way to set build routines for a server on a static color display
is to:

Write your own CreateColormap routines hooked in as pScreen->CreateColormap
which loops through each of the colors in the static map, calling AllocColor
with appropriate rgb values.

(reading on in porting layer document 5.2.7.2 seems to confirm this)

So is this GetStaticColormap a dinosaur or am I missing something
--
Michael Toy, secret identity: the XMAN at Silicon Graphics
Someday: mtoy@xman.sgi.com		For now: {ames,decwrl,sun}!sgi!mtoy