Xref: utzoo comp.sys.amiga.programmer:4424 comp.sys.amiga.misc:4483
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.misc
Subject: Re: My Tablet Program Broke
Message-ID: <22336@cbmvax.commodore.com>
Date: 11 Jun 91 18:08:30 GMT
References: <1991May30.072335.9941@netcom.COM> <1991May31.022526.24625@monu0.cc.monash.edu.au> <1043@celia.UUCP> <22252@cbmvax.commodore.com> <1052@celia.UUCP>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.
Lines: 29

In article <1052@celia.UUCP> celia!neil@usc.edu (Neil Richmond) writes:
>In article <22252@cbmvax.commodore.com> peter@cbmvax.commodore.com (Peter Cherna) writes:
>If this was incorrect, what is correct? To use IECLASS_RAWMOUSE whenever
>I am sending mouse key events and IECLASS_POINTERPOS whenever I send x 
>and y coordinates to the mousepointer? There is VERY LITTLE reference to
>IECLASS_POINTERPOS in the RKM1.3 Manuals. I read that IECLASS_POINTERPOS
>was converted anyway in RAWMOUSE with the correct relative values. What
>happens in 2.0?  

IECLASS_POINTERPOS now officially supports IECODE_xBUTTON stuff.  It
did in 1.3, lost it in early 2.0 (it fell out because it wasn't
defined to work), and now once again does.  It will continue to do so.

>Is it a good thing that side effect was lost?

The side-effect is back, and it does no harm to the system to leave it
that way.  You may continue to use IECLASS_POINTERPOS with IECODE_xBUTTON,
since most everyone that has 2.0 will end up with 2.04 soon.

>Neil F. Richmond         INTERNET: celia!neil@usc.edu

     Peter
--
Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Gosh, didn't he have anything positive to say at all?"