| Re: [AD] acquire_bitmap weirdness |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] acquire_bitmap weirdness
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Mon, 2 Jan 2006 16:33:16 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=RLWpDBazwGegKlPmSIOZJpABfzbrqEcLz+yrCU8Xbknpr4DEXvEccLLJkPs8uc9S8Ipu+A4sHsGboaIkpx6jrKtRPGBs13osDK88YURqRnyR8D3rcwhsjM4z/O9afj/pPrt6SKYTc4rtEddGA0zO7izhPbmmABESGlDcTRmmTuU=
On Monday 02 January 2006 05:15, Elias Pschernig wrote:
> + Note: For backwards compatibility, the unlocking behavior of such
> functions
> + is permanent. That is, if you call acquire_bitmap first, then
> call e.g. en
> + accelerated blit, the DirectX bitmap will be unlocked
> automatically.
This is a little misleading. As I understand it, the lock count still remains
even though it's unlocked. So even if an accelerated function unlocks a
bitmap, you still need to call release_bitmap for every acquire_bitmap you
called.