Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!rutgers!cmcl2!esquire!baumgart From: baumgart@esquire.dpw.com (Steve Baumgarten) Newsgroups: comp.sys.mac.apps Subject: Re: MacDraw II's background activity Message-ID: Date: 2 Apr 91 17:41:58 GMT References: <1CE00001.bfaigj7@tbomb.ice.com> <8336@skye.cs.ed.ac.uk> <251@claris.com> Sender: news@DPW.COM Organization: Davis Polk & Wardwell Lines: 29 In-reply-to: rick@claris.com's message of 30 Mar 91 21:38:35 GMT In article <251@claris.com> rick@claris.com (Rick Boarman) writes: The program itself does very little during idle time. It just tracks the cursor and does some upkeep tasks. What are we doing about this? Well, in MacDraw Pro we have switched over to new system calls that better support MultiFinder (MacDraw II is a fairly old program as far as code goes). We've done a lot to optimize performance and help manage memory better. For instance, MacDraw II keeps an offscreen buffer the same size and bit depth as the monitor. We now crop the buffer as the window size shrinks and we don't let it grow too big. These sound like great improvements, and I'm looking forward to MacDraw Pro. But there have been several times when MacDraw II 1.1 on a IIci running 6.0.7 (no INITs; running either Finder or Multifinder) just seems to take forever to respond to user events of any kind. Clicking causes the pointer to change to the hand cursor -- which then stays that way for a second or two before changing back into the pointer. It's fabulously annoying when it happens.... Anyway, we'll be getting Pro when it's released, and I suspect that will be the end of our problems. Thanks for the info. -- Steve Baumgarten | "New York... when civilization falls apart, Davis Polk & Wardwell | remember, we were way ahead of you." baumgart@esquire.dpw.com | cmcl2!esquire!baumgart | - David Letterman