Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!dogie!uwvax!puff!cat28!blochowi
From: blochowi@cat28.CS.WISC.EDU (Jason Blochowiak)
Newsgroups: comp.sys.apple
Subject: Re: Multitasking, IIgs etc
Summary: Switcher would be difficult
Keywords: Switcher
Message-ID: <2526@puff.cs.wisc.edu>
Date: 6 Apr 89 18:37:07 GMT
References: <9433@claris.com>
Sender: news@puff.cs.wisc.edu
Reply-To: blochowi@cat28.CS.WISC.EDU (Jason Blochowiak)
Organization: U of Wisconsin CS Dept
Lines: 22


	You mentioned the tool StartUp, and ShutDown, and such. But... First
off, what about HeartBeat tasks? What about vectors? What about the
softswitches? As an example of why the softswitches would have to be played
with: What if one application were running in 320 mode and another was in
640? (ok, so maybe that's not softswitches, but it's close :) Also, even if
the tools' DP areas were swapped, they can certainly allocate memory on their
own - are we sure they keep everything "based" in the DP? (e.g. The pointer
to the first window) Even if they do, mightn't they do a DisposeAll on an
AuxID under certain conditions? If they don't, how do we know they won't at
some point in the future? Oh, what about the DOC RAM? (and state)

	Sorry to sound so damned negative, but I've thought this through (I
do think it'd be nice to have at least a Switcher for the //gs), and it seems
as if there's just too much stuff to keep track of... The other thing is that
up to this point, switchEvt hasn't meant much - it's even ignored in Apple's
sample code, so it wouldn't seem that there'd be many apps that would do things
to be switcher aware.
 ------------------------------------------------------------------------------
		Jason Blochowiak (blochowi@garfield.cs.wisc.edu)
			"Not your average iconoclast..."
 ------------------------------------------------------------------------------