[interfacekit] Re: BBitmap allocation
- From: DarkWyrm <bpmagic@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Sat, 16 Feb 2002 13:43:07 -0500
> What exactly are our purposes? :) What qualities do you need out of
>this particular memory allocator?
>
> Graham
I'm not exactly sure what the qualities should be, so I'll just reiterate our
needs. BBitmaps utilize areas for the frame buffer. If we the undocumented
constructor which takes BBitmap flags, each BBitmap has its own area. OTOH,
using the one documented constructor uses the same area for all BBitmaps in a
way much like a regular heap, resizing it to contain all existing BBitmaps.
The bonus with this method is better usage of memory, being quite a few
BBitmaps are less than 4K in size. George Hoffman wrote a memory manager to
handle such things.
It doesn't matter where in the server area the bitmap is stored. All we'll
probably need is just an offset for the server to pass back to the
application in question and the area in which the bitmap is stored. Hope this
gives everyone a better idea of what we'll need.
--DW
- Follow-Ups:
- [interfacekit] CppUnit frustrations
- From: DarkWyrm
- References:
- [interfacekit] Re: BBitmap allocation
- From: Graham Gilmore
Other related posts:
- » [interfacekit] BBitmap allocation
- » [interfacekit] Re: BBitmap allocation
- » [interfacekit] Re: BBitmap allocation
- » [interfacekit] Re: BBitmap allocation
- [interfacekit] CppUnit frustrations
- From: DarkWyrm
- [interfacekit] Re: BBitmap allocation
- From: Graham Gilmore