All geek questions in one place

Does the LoadBitMap () API create paint problems?

I have a legacy system written in C++, MFC. I checked the piece of code in which it LoadBitmap()was replaced with an LoadImage()API. A comment written in the code says: " LoadBitmap()uses the paged pool from the kernel memory, and if the usage reaches the maximum limit, then there will be problems with paint. Therefore, the LoadImageAPI should be used."

I worked a little on this, but did not get much information. When I checked the MSDN , they say: "Please note that using LoadBitmap to load OEM bitmaps is deprecated and is only supported for backward compatibility"

My questions: 1. Are there any problems with the API LoadBitmap()? Why do we prefer LoadImage()over LoadBitmap()? 2. What is OEM bitmaps? Is there a problem if I download regular BMP with LoadBitmap?

+3
source share
1 answer

LoadBitmap() , (DIB). , LoadBitmap() , : " LoadImage ". , LoadBitmap() , , LoadImage() Windows 95! ( , , !)

OEM - , , NULL hInstance lpBitmapName (, OBM_BTNCORNERS, OBM_CHECKBOXES ..). Windows , DrawFrameControl(). , OEM - , , "" .

LoadBitmap(), LoadImage(). LoadBitmap() - , :

LoadImage(hInstance, lpBitmapName, IMAGE_BITMAP, 0, 0, LR_DEFAULTCOLOR);

, , , , , LoadImage(), "LR_CREATEDIBSECTION". "LR_DEFAULTCOLOR" .

+3

Source: https://habr.com/ru/post/1755497/

More articles:


All Articles