...my .png files correctly appear transparent. If I do not, my transparent .png files show black where they should be transparent.
On Win2k and presumably earlier Windows versions, my transparent .png files always look bad. Additionally, it isn't just the .png files I display using wx.StaticBitmap, but also the ones I use in my wx.IconBundle for use as the frame's icon, that appear with black instead of transparent. However, the transparent .pngs used in the toolbar still do render correctly.
Does anyone know the source of this issue and possible workarounds? I just want my transparent .png files to display correctly on all versions of Windows.
...my .png files correctly appear transparent. If I do not, my transparent .png files show black where they should be transparent.
On Win2k and presumably earlier Windows versions, my transparent .png files always look bad. Additionally, it isn't just the .png files I display using wx.StaticBitmap, but also the ones I use in my wx.IconBundle for use as the frame's icon, that appear with black instead of transparent. However, the transparent .pngs used in the toolbar still do render correctly.
Does anyone know the source of this issue and possible workarounds? I just want my transparent .png files to display correctly on all versions of Windows.
Using the maifest causes windows to load the new version of the common controls DLL for the exe. If you don't use the manifest then it loads the old version of the DLL, which I think is the same one that comes with win2k. In the old DLL the native widget used for the static bitmap class (and probably some other places as well) does not recognize the alpha channel in the bitmap, but the version in the new DLL does. It's as simple as that. There are also some other things that are also triggered on whether the manifest is present or not. One way to deal with this is to use the generic static bitmap class in wx.lib.statbmp.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Using the maifest causes windows to load the new version of the common controls DLL for the exe. If you don't use the manifest then it loads the old version of the DLL, which I think is the same one that comes with win2k. In the old DLL the native widget used for the static bitmap class (and probably some other places as well) does not recognize the alpha channel in the bitmap, but the version in the new DLL does. It's as simple as that. There are also some other things that are also triggered on whether the manifest is present or not. One way to deal with this is to use the generic static bitmap class in wx.lib.statbmp.
Boy I wish the average Windows user would realize what a stuck-in-the-20th-century-pile-of-doo-doo Microsoft's operating system is. Yesterday I had the ugly deed of installing Microsoft Office on a client's system, and then updating it with the latest service packs over the web. Total time: over 45 minutes because it kept prompting for the original installation cd (I had to shuffle between cd 1 and cd 2) and reboot at least twice when the competition (OpenOffice) would have let me just download the update and install in a few minutes.
Now I find out that Windows XP only supports transparent bitmaps using the new common controls... sheesh! This stuff works beautifully out of the box on Mac and Linux.
Anyway, thanks Robin. I think I'll just make a non-transparent set of my graphics for Windows and be done with it.
Using the maifest causes windows to load the new version of the common controls DLL for the exe. If you don't use the manifest then it loads the old version of the DLL, which I think is the same one that comes with win2k. In the old DLL the native widget used for the static bitmap class (and probably some other places as well) does not recognize the alpha channel in the bitmap, but the version in the new DLL does. It's as simple as that. There are also some other things that are also triggered on whether the manifest is present or not. One way to deal with this is to use the generic static bitmap class in wx.lib.statbmp.
Boy I wish the average Windows user would realize what a stuck-in-the-20th-century-pile-of-doo-doo Microsoft's operating system is. Yesterday I had the ugly deed of installing Microsoft Office on a client's system, and then updating it with the latest service packs over the web. Total time: over 45 minutes because it kept prompting for the original installation cd (I had to shuffle between cd 1 and cd 2) and reboot at least twice when the competition (OpenOffice) would have let me just download the update and install in a few minutes.
Now I find out that Windows XP only supports transparent bitmaps using the new common controls... sheesh! This stuff works beautifully out of the box on Mac and Linux.
Anyway, thanks Robin. I think I'll just make a non-transparent set of my graphics for Windows and be done with it.
You could help get the message out by making the non-transparent version of your images incorporate the steaming-pile-of-doo-doo theme.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Using the maifest causes windows to load the new version of the common controls DLL for the exe. If you don't use the manifest then it loads the old version of the DLL, which I think is the same one that comes with win2k. In the old DLL the native widget used for the static bitmap class (and probably some other places as well) does not recognize the alpha channel in the bitmap, but the version in the new DLL does. It's as simple as that. There are also some other things that are also triggered on whether the manifest is present or not. One way to deal with this is to use the generic static bitmap class in wx.lib.statbmp.
Boy I wish the average Windows user would realize what a stuck-in-the-20th-century-pile-of-doo-doo Microsoft's operating system is. Yesterday I had the ugly deed of installing Microsoft Office on a client's system, and then updating it with the latest service packs over the web. Total time: over 45 minutes because it kept prompting for the original installation cd (I had to shuffle between cd 1 and cd 2) and reboot at least twice when the competition (OpenOffice) would have let me just download the update and install in a few minutes.
Now I find out that Windows XP only supports transparent bitmaps using the new common controls... sheesh! This stuff works beautifully out of the box on Mac and Linux.
Anyway, thanks Robin. I think I'll just make a non-transparent set of my graphics for Windows and be done with it.
