Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!husc6!husc4!hadeishi
From: hadeishi@husc4.HARVARD.EDU (mitsuharu hadeishi)
Newsgroups: comp.sys.amiga
Subject: DPaint II processor hogging (was Re: Re: DPaint II brushes)
Message-ID: <2412@husc6.UUCP>
Date: Sun, 28-Jun-87 16:54:33 EDT
Article-I.D.: husc6.2412
Posted: Sun Jun 28 16:54:33 1987
Date-Received: Sun, 28-Jun-87 20:36:18 EDT
References: <8706280142.AA22412@ingres.Berkeley.EDU> <8706281237.AA15423@cogsci.berkeley.edu>
Sender: news@husc6.UUCP
Reply-To: hadeishi@husc4.UUCP (mitsuharu hadeishi)
Organization: Harvard Univ. Science Center
Lines: 23

In article <8706281237.AA15423@cogsci.berkeley.edu> bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes:
>uShow handles anything from a tiny brush up to an overscan picture.
>If you wanted to add to uShow you could put in support for color
>cycling chunks,  scrolling a larger-than-overscan picture, and (of
>course) add a user interface.

	uShow crashed on a DPaint II file I tried recently; the file
might have been corrupt, but uShow apparently doesn't do error checking.  My
more full-blown IFF reader doesn't crash at all on this file, and it loads
fine (looks fine).  I would rather have a slightly larger program that
didn't crash.

>Tip-of-the-day:  Dpaint II often hogs the processor even when inactive (at
>least my version does).  To temprarily eliminate this, open a disk requester,
>that part of Dpaint II works properly.

	Actually, Dan has code to avoid the busy-wait, it's just that it
is only active when DPaint is ACTIVE (i.e., when you're doing something)
and due to a mistake it gets circumvented when DPaint is inactive (funnily
enough.)  He is aware of this, and the fix will be released in a future
update.  BTW, the next revision will have code to support the next SlideShow.

					-Mitsu