As title, now already overloaded ListControl controls DrawItem message and to draw some graphics on them, the tracing point is GDI drawing mode, set up ListControl itself comes with a double buffer drawing method, SetExtendedStyle (LVS_EX_DOUBLEBUFFER); But when complex graphics, drawing will occupy too much memory, the issues that led to the interface card, ask how to solve this problem?

CodePudding user response:

Does not recommend the use of GDI tracing point model, addressing it make a lot of time, can according to the bitmap data populated in memory, again, according to the reference CDib class
Every time to draw different content? If not, it is good to draw on the bitmap memory, draw a, multiple map using

CodePudding user response:

reference 1st floor zgl7903 response:

does not recommend the use of GDI tracing point model, addressing it make a lot of time, can according to the bitmap data populated in memory, again, according to the reference CDib class
Every time to draw different content? If not, it is good to draw on the bitmap memory, draw a, multiple map using

Right, because each item to draw graphics are not the same, if it is in the DrawItem using double buffer memory bitmap drawing method and DrawItem news have conflict? As if can't be displayed, CDib class? Can you give an application example, did not know this before?

CodePudding user response:

See if there is a memory leak phenomenon, memory leak can lead to draw more and more caton

CodePudding user response:

The

reference tree senior 3 floor response:

and see if there is a memory leak phenomenon, memory leak can lead to draw more and more caton

Memory leak is certainly not,

CodePudding user response:

http://www.codeforge.com/read/5765/cdib.h__html
http://www.codeforge.com/read/5765/cdib.cpp__html