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: Layers problem
- Date: 3 Jan 1996 14:43:31 +0100
- Organization: dis-
- Message-ID: <4ce163$hjj@serpens.rhein.de>
- References: <4cdrup$gqj@ousrvr3.oulu.fi>
- NNTP-Posting-Host: serpens.rhein.de
-
- kinnunen@stekt.oulu.fi (Teijo Kinnunen) writes:
-
- >I have a bizarre problem with using layers.library, which I haven't yet
- >been able to solve.
-
- > DeleteLayer(0,la);
-
- This is the culprit.
-
- >Anyway, it does not work. The allocation seems to work fine, but the
- >FreeBitMap() call corrupts memory. (At least if the program is run a
- >couple of times. Enforcer can be used, but Mungwall causes the bug to
- >vanish.)
-
- DeleteLayer erases the region that the layer did occupy. This
- may or may not cause some blitter activity. You must not free
- the bitmap until the queued blitter operation has finished.
-
- A WaitBlit() before calling FreeBitMap() should solve your problem.
-
- Another possibility is to install a dummy backfill hook for the
- Layer_info with InstallLayerInfoHook().
-
- Regards,
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-