Take a look at the below two posts:
http://forum.codejock.com/forum_posts.asp?TID=18822&PID=66280&title=cxtpimagemanagerresamplealphalayer-correction#66280 - http://forum.codejock.com/forum_posts.asp?TID=18822&PID=66280&title=cxtpimagemanagerresamplealphalayer-correction#66280
http://forum.codejock.com/forum_posts.asp?TID=18959&PID=66333&title=bug-cxtpgraphicbitmappng#66333 - http://forum.codejock.com/forum_posts.asp?TID=18959&PID=66333&title=bug-cxtpgraphicbitmappng#66333
I have fixed the isues & would like to see hotfixes in the next releases:
Attached hotfixes files: uploads/6515/XTPGraphicBitmapPng_+_XTPImageManager_Hotfixes_-_22-o9-2o11.zip - uploads/6515/XTPGraphicBitmapPng_+_XTPImageManager_Hotfixes_-_o1-o1-2o12.zip - uploads/6515/XTPGraphicBitmapPng_+_XTPImageManager_Hotfixes_-_o1-o1-2o12.zip
Thank you for you understand ;)
===============================================================
[EDIT]:
The attached hotfixes files have been updated due to a small mistake concerning DIBs padding bytes.
This happened because Microsoft MSDN published some information about BITMAP structure and about bmWidthBytes member assuming that The number of bytes in each scan line must be divisible by 2, but actually it should be divisible by 4. Source: http://msdn.microsoft.com/en-us/library/dd183371%28v=vs.85%29.aspx - http://msdn.microsoft.com/en-us/library/dd183371(v=vs.85).aspx The count of padding bytes formula for 24 bpp DIBs that I am suggesting would be: -(bmpWidth * 3) & 3 
Hint: Microsoft people should fix their stuff accordingly. 
------------- Product: Codejock ToolkitPro MFC v16.2.0 Platform: Microsoft Windows 8 Pro (64-bit)
Language: Microsoft Visual C++ v6.0 (MFC)
|