On Mon, Nov 18, 2002 at 08:24:59AM +0100, Aaron Ardiri wrote:
> the right api to use is BmpSize() and
> BmpBitsSize() for determining the size of the bitmap structure and an
> individual bitmap.
See also BmpGetSizes(). I'm surprised the documentation for BmpSize()
and BmpBitsSize() does not
> In one of our apps, we do the following:
>
> Errerror = 0;
> WinHandlesaveWinH = NULL;
> BitmapType*bp;
>
> saveWinH = WinSaveBits(bounds, &error);
> bp = WinGetBitmap(saveWinH);
>
> // Validate Image Offset...
> imageSize = MemPtrSize(b
I get this in digest, so before the flame starts, Ben pointed out BmpSize()
:D
Still interested in the second part though.
-MD
> Or How to get the size of a BitmapPtr under OS 5
>
> In one of our apps, we do the following:
>
> Errerror = 0;
> WinHandlesaveWinH =
At 1:37 AM -0500 11/18/02, Matt Disher wrote:
In one of our apps, we do the following:
This works well, actually, on all 3.5/4.x devices and to-date have
experience no ill effects. However in OS/5 the Simulator blows up
big time at the MemPtrSize() function. If there's a better way to
Or How to get the size of a BitmapPtr under OS 5
In one of our apps, we do the following:
Errerror = 0;
WinHandlesaveWinH = NULL;
BitmapType*bp;
saveWinH = WinSaveBits(bounds, &error);
bp = WinGetBitmap(saveWinH);
// Validate I
