Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!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: <7553@sugar.hackercorp.com> Date: 20 Jan 91 15:16:24 GMT References: <1991Jan14.221532.4431@cunixf.cc.columbia.edu> <11719@goofy.Apple.COM> <1991Jan16.061456.15340@zorch.SF-Bay.ORG> <1991Jan16.174416.16308@cunixf.cc.columbia.edu> <1991Jan18.231330.16290@Neon.Stanford.EDU> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 24 In article <1991Jan18.231330.16290@Neon.Stanford.EDU> torrie@cs.stanford.edu (Evan J Torrie) writes: > Often, when a spreadsheet is calculating a huge file, or running a > macro, you want to move around and see other parts of the spreadsheet, > Or given a ray-tracer. I have (on occasion) ray-traced 1024 x 1024 > pictures - but I only have a 640 x 480 monitor. So I often need to > move around (i.e. scroll-bars, i.e. checking for user input) On the Amiga you'd do that by splitting the program into a compute engine and a user interface task. The compute engine runs at full speed without having any code in the main loop to check for user interaction, and the user interface task just sits there waiting for input taking up no CPU time until you need it. Amiga... working smarter means working faster. > Does this slow the program down? > Yes On the Mac it does. On the Amiga it doesn't. -- Peter da Silva. `-_-' .