home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #18 / NN_1992_18.iso / spool / comp / sys / mac / programm / 14077 < prev    next >
Encoding:
Text File  |  1992-08-16  |  1.5 KB  |  39 lines
  1. Newsgroups: comp.sys.mac.programmer
  2. Path: sparky!uunet!sun-barr!apple!mumbo.apple.com!gallant.apple.com!NewsWatcher!user
  3. From: jpugh@apple.com (Jon Pugh)
  4. Subject: Re: FlushEvents necessary? (was: Re: Toolbox init)
  5. Sender: news@gallant.apple.com
  6. Message-ID: <jpugh-160892232829@90.20.3.200>
  7. Date: Mon, 17 Aug 1992 06:32:09 GMT
  8. References: <1992Aug11.152914.18785@uni-paderborn.de> <13992@gazette.bcm.tmc.edu> <hammett.714004576@sbsu1.aukuni.ac.nz>
  9. Organization: Apple Computer, Inc.
  10. Followup-To: comp.sys.mac.programmer
  11. Lines: 26
  12.  
  13. In article <hammett.714004576@sbsu1.aukuni.ac.nz>,
  14. hammett@sbsu1.aukuni.ac.nz (Tim Hammett) wrote:
  15. > 
  16. > ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) writes:
  17. > >>     InitWindows();
  18. > >>     FlushEvents(0xffff,0);
  19. > 
  20. > >Personally I prefer to do a FlushEvents *after* all my program setup.
  21. > 
  22. > Is it necessary to do FlushEvents() at all these days? I notice that most
  23. > of the DTS sample Apps don't. I would be interested in hearing the pros
  24. > and cons of using FlushEvents at program startup.
  25.  
  26. Personally, I feel that you shouldn't need to call FlushEvents, but I can
  27. see
  28. situations where you should.
  29.  
  30. Most notable, the annoying splash screen (we've all made them).  Since some
  31. of these things require a click to dismiss them, if you put one up you
  32. should ALWAYS call FlushEvents afterwards so that the user's click doesn't
  33. hit the desktop and switch him.  Accidentally switching out of a windowless
  34. program is darned annoying.
  35.  
  36. Otherwise, don't flush and let the user start mousing ahead of you.
  37.  
  38. Jon
  39.