Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpda!hpsmtc1!hpisof0!hpsel1!hpindda!grant From: grant@hpindda.HP.COM (Grant Haidinyak) Newsgroups: comp.sys.amiga Subject: Re: Spawning tasks which draw . . . Message-ID: <6570006@hpindda.HP.COM> Date: Thu, 3-Dec-87 00:23:51 EST Article-I.D.: hpindda.6570006 Posted: Thu Dec 3 00:23:51 1987 Date-Received: Mon, 7-Dec-87 05:51:01 EST References: <787@rocky.STANFORD.EDU> Organization: Hewlett Packard, Cupertino Lines: 15 >* Be careful with functions that use the blitter in tasks that you plan >* to RemTask() from the parent (or someone else!) If the blitter is >* allocated when the RemTask() is executed, it will stay allocated and >* the system will lock up tighter than a drum. To fix, simply Forbid()/ >* Permit() around all the blitter using sections (like a sequence of >* Move/Draws.) Wouldn't it be nice, if instead of doing a Forbid/Permit and locking out the multitasking feature of the Amiga, have a pair of routines, something like SetCritical/ResetCritical, which wouldn't allow a task to be aborted Just a thought (my one for the week) Grant