Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!kuhub.cc.ukans.edu!markv
From: markv@kuhub.cc.ukans.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  Window Waiting (was <None> )
Message-ID: <1991May28.163542.31103@kuhub.cc.ukans.edu>
Date: 28 May 91 21:35:42 GMT
References: <1991May24.102345.1@wombat.newcastle.edu.au> <1991May24.092943.31027@kuhub.cc.ukans.edu> <21912@cbmvax.commodore.com> <mykes.2894@amiga0.SF-Bay.ORG>
Organization: University of Kansas Academic Computing Services
Lines: 27

>>The only change that I would make to this is that the ReplyMsg() call
>>should come much sooner.  Let Intuition have it's message back asap....
>>for the NEXT thing it wants to send to you, it will allocate memory
>>for a new one rather than use one already in existance. 

> Or even better is to use a structure assignment to copy the entire contents
> of the message to a private message struct before replying...

True, however, Intuition will only send 1 Refresh or Intuitick at a
time, and a "long time" by computer processing standards isn't
nessescarily too long.  So I only worry about copying if I'm doing
something like FOLLOWMOUSE or like in an editor where I can get a lot of
RAW/VANILLAKEY messages.

Note that if you going off for a real long time its better to
ModifyIDCMP().  INUTITICK by itself works nicely here since you only
get one until you reply, so you can ModifyIDCMP(), reply old
messages, and know only one more will queue up.
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Gooderum			Only...		\    Good Cheer !!!
Academic Computing Services	       ///	  \___________________________
University of Kansas		     ///  /|         __    _
Bix:	  mgooderum	      \\\  ///  /__| |\/| | | _   /_\  makes it
Bitnet:   MARKV@UKANVAX		\/\/  /    | |  | | |__| /   \ possible...
Internet: markv@kuhub.cc.ukans.edu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~