Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!oliveb!amiga!jimm
From: jimm@amiga.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga
Subject: Re: Graphics.library (was transputer board)
Message-ID: <5543@amiga.UUCP>
Date: 11 Apr 90 20:34:40 GMT
References: <02602.AA02602@sosaria.imp.com> <8612@hubcap.clemson.edu> <PORTUESI.90Apr4111348@tweezers.esd.sgi.com> <5845.261cc9b7@vax1.tcd.ie> <28715@cup.portal.com> <5849.26208c08@vax1.tcd.ie> <891@mpirbn.UUCP>
Reply-To: jimm@superman.UUCP (Jim Mackraz)
Organization: Commodore-Amiga Inc, Los Gatos CA
Lines: 23

In article <891@mpirbn.UUCP> p554mve@mpirbn.UUCP (Michael van Elst) writes:

)Nevertheless, the current routines did one thing that made them 'safe'
)to use. They work synchronous so that you can free the bitmaps they are working
)on after the call returns.

That is not true for the Amiga graphics.library routines, in general.
You must do WaitBlit() after a routine if you need to know that the blit
is done.

)An optimized routine could use the time and calculate the next blit in
)advance.

Yep, that's what happens today.  The routines call WaitBlit() BEFORE
they use the blitter, but not after.

	jimm

-- 
--------------------------------------------------	- opinions by me
"This voice console is a *must*.  I press Execute. 
 `Hello, I know that you've been feeling tired.
  I bring you love and deeper understanding.' "		-lyrics by Kate Bush