Hi Vitaliy,
I'm also working on a corruption problem that occurs in Visio's toolbars. It seems that we don't draw transparent images properly sometimes. The case that appears to be screwing up is when the imagelist's default background colour is CLR_NONE, and an image is drawn with CLR_DEFAULT as the background. The image gets random junk drawn where hbmMask is nonzero.
I think you're right about DIBSections... we should create and use them. The programmer who originally implemented Imagelist probably didn't know about it...
Mike
Vitaliy Margolen wrote:
For past few days I was trying to figure out what is the problem with corrupt bitmaps. Here is my findings: 1. _read_bitmap does is not work right. The for() loop where it's restructuring original bitmap from multi-row into single-row. 2. Windows creates DIBSection to keep original bitmap so it could be saved as is. This is not used that often. However development tools do use it. For example: Delphi.
I have few questions before making any hacking: - Why do we use single row bitpams versus multi-row like native? - Why we not creating DIBSection?
