Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bu.edu!xylogics!merk!alliant!linus!linus!mbunix.mitre.org
From: laf@mbunix.mitre.org (Lee Fyock)
Newsgroups: comp.sys.mac.programmer
Subject: Re: An itsy bitsy question...
Message-ID: <127611@linus.mitre.org>
Date: 8 Jan 91 13:35:22 GMT
References: <La6cV1w164w@questor.wimsey.bc.ca> <27725.2787e3d0@kuhub.cc.ukans.edu> <1991Jan8.043323.954@santra.uucp>
Sender: usenet@linus.mitre.org
Organization: The MITRE Corporation
Lines: 12
Nntp-Posting-Host: asgard.mitre.org

I've found that an easier way to avoid flicker (easier than using
background bitmaps, etc.) is to just put in a check to see if the
mouse has moved before erasing and redrawing the line.  This is
extremely flicker-free, with very little code.  It isn't, of course,
very multifinder friendly.  What happens to the GetNextEvent version
of this code if the user clicks on the multifinder icon in the
menu bar and the program gets switched out?  It won't know it
because app4events aren't being read, right?

Thanks,
Lee Fyock
laf@mbunix.mitre.org