Re: 32-bit bitmap resources - pixel data
From: le ténébreux (prince.d'aquitaine_at_tour.abolie)
Date: 12/28/04
- Previous message: Severian: "Re: 32-bit bitmap resources - pixel data"
- In reply to: Severian: "Re: 32-bit bitmap resources - pixel data"
- Messages sorted by: [ date ] [ thread ]
Date: 28 Dec 2004 19:35:50 +1050
Severian <severian@chlamydia-is-not-a-flower.com> wrote:
>> Does this mean that the resource is now permanently in memory
>> until the program terminates? Or was it taking up memory anyway,
>> even before Load/LockResource() ?
>
> UnlockResource/FreeResource are no longer necessary. The resource is
> always mapped into your virtual address space; the data will be paged
> in automatically when referenced, and page out as not needed, just
> like the executable program sections (.text). LockResource() is still
> required, but all it really does is convert the HGLOBAL to a pointer.
>
> So, your resources are taking up *virutal address space*, but only
> occupying real memory when needed.
Excellent. Thanks very much for clearing that up.
- Previous message: Severian: "Re: 32-bit bitmap resources - pixel data"
- In reply to: Severian: "Re: 32-bit bitmap resources - pixel data"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|