home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: ChangeScreenBuffer()
- References: <4gl1e7$r6s@oreig.uji.es>
- X-Newsreader: TIN [version 1.2 PL2]
- Path: imada.ou.dk!breese
- From: breese@imada.ou.dk (Bjorn Reese)
- Message-ID: <1996Feb24.154556.15537@imada.ou.dk>
- Sender: news@imada.ou.dk
- Nntp-Posting-Host: wagner.imada.ou.dk
- Organization: Dept. of Math. & Computer Science, Odense University, Denmark
- Date: Sat, 24 Feb 1996 15:45:56 GMT
- Newsgroups: comp.sys.amiga.programmer
-
- Jorge Acereda Macia (ii202@rossegat.uji.es) wrote:
-
- > Is this busy-waiting?
- >
- > while(NULL==ChangeScreenBuffer(DBScreen, Bitmap[CurrBuf])) ;
-
- Yes.
-
- > How can I handle this? Doing WaitTOF() each time ChangeScreenBuffer
- > fails?
-
- The official way to handle it is to wait for the safe signals (there's
- some example in NDK called doublebuffer.c, I believe) However, this
- can give some strange results under some circumstances, so I prefer
- WaitTOF().
-
- --
- Bjorn Reese Email: breese@imada.ou.dk
- Odense University, Denmark URL: http://www.imada.ou.dk/~breese
-
- "It's getting late in the game to show any pride or shame" - Marillion
-