Path: utzoo!utgpu!watmath!clyde!att!ucbvax!ucsd!sdcc6!sdcc10!cs161agc
From: cs161agc@sdcc10.ucsd.EDU (John Schultz)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Unsupported Programming Practices
Message-ID: <43@sdcc10.ucsd.EDU>
Date: 8 Jan 89 20:11:37 GMT
References: <8901060406.AA22607@postgres.Berkeley.EDU> <84277@sun.uucp>
Reply-To: cs161agc@sdcc10.ucsd.edu.UUCP (John Schultz)
Organization: University of California, San Diego
Lines: 24

In article <84277@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes:
>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.
>--Chuck McManis

  Just do a WaitBlit().  OwnBlitter probably calls WaitBlit(),
then you'll also have to call DisownBlitter() before you call any
rom routines.
  For custom blitter stuff, I've always done:

    WaitBlit();
    OwnBlitter();
     // do custom blits
    DisownBlitter();


  Does OwnBlitter() actually call WaitBlit()? Or will it blow up if
OwnBlitter is called without first calling WaitBlit()?


  John Schultz