Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.advocacy Subject: Re: How do we change the scheduler? (Was Re: Multitasking at home...) Message-ID: <7600@sugar.hackercorp.com> Date: 24 Jan 91 12:34:38 GMT References: <1991Jan18.231330.16290@Neon.Stanford.EDU> <7553@sugar.hackercorp.com> <1991Jan21.004720.25985@ncsuvx.ncsu.edu> <12880@life.ai.mit.edu> <1991Jan21.055854.14130@rice.edu> <7589@sugar.hackercorp.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Distribution: usa Organization: Sugar Land Unix - Houston Lines: 16 I said: > On the Mac a program waiting for a keypress > has to sit there and handle all the events coming into it from WaitNextEvent. Now someone from Apple sent me mail disputing this. Yes, the task can ignore any but keypress inputs, but if it does that its window will not be properly updated: it's the applications responsibility for managing its own window, and obscured sections of that window will not be repainted when windows in front of it disappear. I suspect that other aspects of the application's user interface will break until it starts listening for display events again, but in any event it's not practical for a Mac task to just ignore everything but keypresses, so I doubt much, if any, real software does. -- Peter da Silva. `-_-' .