[VB6] Icon Resource Organizer

[petersen]

Not related to the current thread topic, but related to AlphaImage mentioned above. I've downloaded AlphaImage zip. Because I can't readily run it (as it is for OCX), so I take a quick look at the code block concerning WMF/EMF. There is a small point I wish to raise (before you wind up your revision of AlphaImage).

Please set your Windows to Large Font, i.e. 120 DPI, test a WMF/EMF to see whether the size you obtain (reported by your OCX) is the same as you would in a normal 96 DPI screen. If not, you may wish to adjust the width and height downward by a factor of "96 / 120" whereas 120 is the actual screen resolution you would obtain from a Windows API call.

I raise this point because most people omit to address it in their code dealing with stdPicture size for WMF/EMF.

[LaVolpe]

Please set your Windows to Large Font, i.e. 120 DPI, test a WMF/EMF to see whether the size you obtain (reported by your OCX) is the same as you would in a normal 96 DPI screen. If not, you may wish to adjust the width and height downward by a factor of "96 / 120" whereas 120 is the actual screen resolution you would obtain from a Windows API call.

I raise this point because most people omit to address it in their code dealing with stdPicture size for WMF/EMF.

I'll look at it later, but don't expect any issues. WMF/EMF are not being processed as such. I know how to scale the metafile from its contained resolution parameters for the current DPI. But WMF/EMF do not work well in GDI+ when wanting to manipulate the image, i.e., can't grayscale metafiles with GDI+. So, internally, WMF/EMF are saved to PNG for display. GDI+ when saving metafile to another format, calculates the size in relation to DPI during the process.