Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!usc!elroy!gryphon!keithd
From: keithd@gryphon.COM (Keith Doyle)
Newsgroups: comp.sys.amiga.tech
Subject: Overhead of REPORTMOUSE
Message-ID: <15103@gryphon.COM>
Date: 25 Apr 89 08:55:56 GMT
Reply-To: keithd@gryphon.COM (Keith Doyle)
Distribution: comp
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 26


Got a question for one of the guru's  (Dale?  Jimm?), hope it
hasn't just been asked to death and I missed the responses.

Is there any extra overhead incurred when setting NewWindow.Flags with
REPORTMOUSE if MOUSEMOVE is not turned on in the IDCMP, versus a window
that doesn't have REPORTMOUSE set?

The kind of overhead I'm referring to here is having a lot of continuous
mouse messages going through a bit of extra processing before just being
thrown away because MOUSEMOVE isn't turned on.   Processing that isn't
being done when REPORTMOUSE is off.

If there is, is there any way to dynamically turn REPORTMOUSE on and
off in a Window?  Can I just set Flags directly, or would it be
ignored or cause problems?



And BTW, did anyone find any problems with Leo's method of starting
up a process without doing a LoadSeg?  If not, I plan to start doing
some experimentation in that area. 


Keith Doyle
keithd@gryphon.COM    gryphon!keithd     gryphon!keithd@elroy.jpl.nasa.gov