CFbsBitmap in SDK 3.0 Seems not allow using DataAddress()

[kenwc]

I'm porting my project from SDK 2.0 to SDK 3.0. in the early version. you can call CFbsBitmap:ataAddress() to get the pointer to bitmap. and manipulate the contents of this bitmap.
But after SDK 3.0, whenever you call CFbsBitmap:ataAddress(). It will crash. I wonder maybe SDK 3.0 simply dosen't allow direct bitmap acccess.

---------------------------------------------------------------------
you can test the following codes yourself
---------------------------------------------------------------------
CFbsBitmap bitmap;
TUint8 *bmpData=NULL;
TInt iErr=bitmap.Create(TSize(176,208) , EColor64K);

if(!iErr)
bmpData=(TUint8 *)bitmap.DataAddress();
---------------------------------------------------------------------

It will crash in the line bmpData=(TUint8 *)bitmap.DataAddress(). But if you create smaller bitmap, for example 100*100. these codes will work.

[ptrmn]

I haven't had a problem with DataAddress() in 3rd edition, and I'm using larger bitmaps than that.

[Greg_Jokiel]

Hi,

It is a good practice to call CFbsBitmap::LockHeap () before and CFbsBitmap::UnlockHeap () after you call CFbsbitmap:ataAddress () and use it to prevent the Font and Bitmap server to rearrange the heap.

A crash can sometimes occur if you don't even under 2nd edition SDK.

GreG

[bitnir]

If the crash code is FBSCLI 22 the lack of LockHeap is to blame. I would use LockHeap/Unlockheap always with DataAddress.

[kenwc]

Hi,

It is a good practice to call CFbsBitmap::LockHeap () before and CFbsBitmap::UnlockHeap () after you call CFbsbitmap:ataAddress () and use it to prevent the Font and Bitmap server to rearrange the heap.

A crash can sometimes occur if you don't even under 2nd edition SDK.

GreG

Thank you. It is really the answer of my question. It is solved now.

[khumen]

Hi,
It is a good practice to call CFbsBitmap::LockHeap () before and CFbsBitmap::UnlockHeap () after you call CFbsbitmap:ataAddress ()
GreG

Thanks a lot, this really help with 3rd edition SDK

WBR,
Dmitry Gazko

[olhed]

You should _always_ use LockHeap/UnlockHeap, also on 2nd edition and earlier.

If it works, its just pure luck.

With EKA2, the chances for it to go wrong increased a lot, because of improved multitasking.

Because of this, and probably because there was so many useing DataAddress without locking heap, they added a panic if you try to call DataAddress without LockHeap/UnlockHeap.

ALWAYS use LockHeap/UnlockHeap, even in your projects for old platforms.
SPECIALLY if you write to the bitmap. If you don't, you run the risk to corrupt the Fbs Heap and crash not only your own app but the whole phone.