home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Doublebuffered window??
- References: <4bfe05$l11@katiska.clinet.fi> <4bgmqq$kh6@serpens.rhein.de> <4cmftc$1g1@sunsystem5.informatik.tu-muenchen.de> <4cmrgp$5bs@serpens.rhein.de> <4d69m8$i0h@sunsystem5.informatik.tu-muenchen.de>
- Date: 15 Jan 1996 13:50:23 +0100
- Organization: dis-
- Message-ID: <4ddiif$80o@serpens.rhein.de>
- NNTP-Posting-Host: serpens.rhein.de
-
- fischerj@informatik.tu-muenchen.de (Juergen "Rally" Fischer) writes:
-
- >Non-busy-wait WaitBoWin would have been a very useful lib-routine...
-
- No, because task scheduling doesn't guarantee that you are still at
- the same beam position when your task gets to run. What you want is
- an interrupt that starts the blitter. This is the QBSBlit() function
- which, unfortunately, isn't really high level. The other possibility
- is to use a Bob. Bob rendering is synchronized to the display.
-
- >I guess they also sync with vblank ?
-
- They sync even to the Bob position.
-
- >The only non-chipset-only method I see is dealing with VBeamPos
-
- Other display devices might not even have a valid VBeamPos().
-
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-