Path: utzoo!attcan!uunet!sdrc!thor!scjones
From: scjones@thor.UUCP (Larry Jones)
Newsgroups: comp.windows.x
Subject: Pixmap serialNumber assignment
Message-ID: <199@thor.UUCP>
Date: 16 Oct 90 14:32:19 GMT
Organization: SDRC, Cincinnati
Lines: 19

I'm in the process of implementing a server over top of another
graphics system and I've been using serialNumber as a unique
identifier for graphics system resources I create but I just ran
into a snag and I'm not sure whether it's a bug or not.  When a
client creates a pixmap, ProcCreatePixmap in dix/dispatch.c calls
the screen's CreatePixmap procedure which assigns a serial number
to the newly-created pixmap, but then ProcCreatePixmap assigns it
a new serial number which screws up my mapping.

The porting layer document says that CreatePixmap is responsible
for filling in *all* the fields in the pixmap, so it seems to me
that dix shouldn't be mucking about with it.  Am I right?
----
Larry Jones                         UUCP: uunet!sdrc!thor!scjones
SDRC                                      scjones@thor.UUCP
2000 Eastman Dr.                    BIX:  ltl
Milford, OH  45150-2789             AT&T: (513) 576-2070
You can never really enjoy Sundays because in the back of your
mind you know you have to go to school the next day. -- Calvin