Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!agate!sprite.berkeley.edu!kupfer
From: kupfer@sprite.berkeley.edu (Mike Kupfer)
Newsgroups: comp.windows.x
Subject: pointer mismatch in pmax mfb code?
Message-ID: <1991Feb6.071010.23625@agate.berkeley.edu>
Date: 6 Feb 91 07:10:10 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Followup-To: comp.windows.x
Organization: University of California, Berkeley
Lines: 14


In R4, ddx/dec/mfbpmax/mfbpmax_io.c:pmSetCursorPosition does a call
through pmPointer->processInputProc, passing in pmPointer.  The
routine it calls is dix/events.c:ProcessPointerEvent.  pmPointer is a
DevicePtr; the corresponding parameter in ProcessPointerEvent is a
DeviceIntPtr.  This appears to be a type mismatch.  Is there something
I'm missing, or is this a bug?  (The sources I have access to are
slightly hacked, but in this case I think they're the same as the
canonical sources.)

Thanks in advance for any light you can shed on this for me.

Mike Kupfer
kupfer@sprite.berkeley.edu