Path: utzoo!utgpu!attcan!uunet!lll-winken!ames!oliveb!amiga!boing!dale
From: dale@boing.UUCP (Dale Luck)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Unsupported Programming Practices
Message-ID: <579@boing.UUCP>
Date: 7 Jan 89 07:15:13 GMT
References: <8901060406.AA22607@postgres.Berkeley.EDU> <84277@sun.uucp>
Reply-To: dale@boing.UUCP (Dale Luck)
Organization: Boing, Milpitas, Ca.
Lines: 24

In article <84277@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes:
>In article <8901060406.AA22607@postgres.Berkeley.EDU> (Matt Dillon) writes:
>> Is there some call one can make which ensures any blitter usage from the 
>> previous graphics library call will complete before returning?
>
>Would OwnBlitter() work for this? I assume that the sequence :
>	Draw(...);
>	OwnBlitter();
>Can't possibly give you the Blitter before the Draw call has finished
>with it.
>

Nope, not true. OwnBlitter returns when you have logical control of
the blitter. However the blitter may still be finishing up the last
blit. You need to use WaitBlit().

Draw will return after firing off the last blit which is usually the
last plane. However Draw does not wait for the blitter to finish
before Disowning the blitter. This is done to achieve as great amount
of overlap of cpu cycles and blitter cycles as possible.

-- 
Dale Luck     GfxBase/Boing, Inc.
{uunet!cbmvax|pyramid}!amiga!boing!dale