Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!andrew.cmu.edu!dp1g+
From: dp1g+@andrew.cmu.edu (Demetri Patukas)
Newsgroups: comp.sys.amiga.tech
Subject: Re: ReportMouse() problems!
Message-ID: <cXXkTNy00WB7R=fHBA@andrew.cmu.edu>
Date: 26 Nov 88 19:36:57 GMT
Organization: Carnegie Mellon
Lines: 20

Thanks for quick replies from <aozer@NeXT.com> and
<riley@tcgould.tn.cornell.edu> about my ReportMouse problems.

*** solution to problem#1: It seems that, contrary to the
documentation, the arguments are reversed (that is,
ReportMouse(FLAG,window)).  This works.

My other problem (with ModifyIDCMP) turned out to be that I was
checking for flag bits on the Code field, and this is apparently a
no-no (you should just check for straight values).  As it turns out,
(SELECTDOWN & SELECTUP)==SELECTDOWN, so I always fell through and
turned off mouse events.

*** solution to problem #2: ModifyIDCMP does work as advertised.  My
problem was that I used & (ampersand) to check the Code field of a
MOUSEBUTTONS message, but I should have used ==.

Thanks again,

        demetri <dp1g@andrew.cmu.edu>