That's fine....as long as the OP remembers to adjust his/her direct pixel access calculations accordingly :) Mark Salsbery Microsoft MVP - Visual C++ :java:

8 bit per pixel in RGB format

jossion wrote: the declaration for ppbits was void **ppbits The above is wrong. You have to declare a pointer to void, for instance void * pbits; and then pass the address of the pointer (i.e. &pbits) to CreateDIBSection: CreateDIBSection(hDC,bitmap,DIB_PAL_COLORS, &pbits, NULL,0); :) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke

Thanks for the valuable information

In addition to CPallini's reply... I would recommend using messages ID(s) in the range WM_APP through 0xBFFF instead of a WM_USER-based ID as shown in the MS sample code. That way there's much less of a chance your message will conflict with any messages used by certain private window classes. You can also get a system-wide unique message ID with RegisterWindowMessage(). Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

HBITMAP CreateBitmap( int nWidth, // bitmap width, in pixels int nHeight, // bitmap height, in pixels UINT cPlanes, // number of color planes UINT cBitsPerPel, // number of bits to identify color CONST VOID *lpvBits // color data array ); Have a look at the CreateBitmap (shocking name, I know) command - you can specify a pointer to data which will make up the bitmap. There are some issues with it - you'll need the data to match the bits per pixel, etc. Or CreateDIBitmap may be better for you. You'll have to transform you data into a format those command will be happy with though - and how hard that is depends on how "friendly" your format is. If you search codeproject by author for PJ Arends, you can use his Image Viewer article to help you. It's great if you're fiddling about with DCs, and Bitmaps - it's saved hours of development for me in the past. Iain.

jossion wrote: I am using CreateThread() function to create worker threads. Are there any other ways to create threads in MFC applications. With MFC, you should be using AfxBeginThread(). "Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

That address is in one of the OS DLLs. If you can repro the crash, run the EXE in the debugger and look at the stack trace when the crash happens. You can then look up the addresses that are on the stack. --Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?

jossion wrote: How to initialize pointers such as int *temp_array and int **double_array int *temp_array pTemparray = NULL; int **double_array pDoublearray = NULL; Failure is not an option - it's built right in.

Thanks a lot for the good link

Case 2 could lead to a leak because your "else if" chain has no final else clause. If none of the conditions apply, sub_code will never be freed. You could just add at the end else free(sub_code); and that would take care of it.

Thanks a lot for the detailed suggestions. I will be back after a detailed study of those.