0

I'm wondering , if I want to create different bitmaps,

I use the CreateCompatibleBitmap function again and again, to associate it to the same memory CDC.

is it the same meaning that I CreateBitmap and SelectObject again and again??

I ask this question because I want to do something to the newly created bitmap by another CDC.

Steven Shih
  • 645
  • 1
  • 10
  • 22
  • What's your actual problem? Are you just worried about resource use or are you unable to do what you want? – snowdude Aug 23 '12 at 10:55
  • I see some code with CreateCompatibleBitmap first, then use SelectObject again. If it is the same, then I don't want to do the same thing again. – Steven Shih Aug 23 '12 at 23:15

2 Answers2

2

Without seeing the specific code it's hard to know the exact problem but CreateCompatibleBitmap is commonly used in double-buffering situations to avoid flickering. Rather than drawing directly to the Device Context (DC) you first draw to an off-screen, or memory, DC which is basically drawing to a bitmap. The bitmap is then copied directly to the screen DC using BitBlt, so it appears like all the drawing happens at the same time.

The usual steps are this (and will probably happen on every WM_PAINT):

  1. Use the screen DC to create a bitmap, which is 'compatible' with it, using CreateCompatibleBitmap.
  2. Create a memory DC
  3. Select the bitmap into the memory DC (this is what you'll draw to)
  4. When drawing is finished BitBlt the memory DC's bitmap onto the screen DC.

More information available here: Guide to Win32 Memory DC (Code Project)

snowdude
  • 3,854
  • 1
  • 18
  • 27
0

Yes, CreateCompatibleBitmap() creates a new bitmap, a new memory allocation, a new handler each time you call it in a loop;

john k
  • 6,268
  • 4
  • 55
  • 59