When starting a wxHaskell application on Ubuntu, the following messages are given:
17:33:49: Debug: wxColour::Set - couldn't set to colour string 'MEDIUM GREY' 17:33:49: Debug: wxColour::Set - couldn't set to colour string 'MEDIUM GREY' 17:33:49: Debug: Adding duplicate image handler for 'PNG file' 17:33:49: Debug: Adding duplicate image handler for 'JPEG file' 17:33:49: Debug: Adding duplicate image handler for 'TIFF file' 17:33:49: Debug: Adding duplicate image handler for 'GIF file' 17:33:49: Debug: Adding duplicate image handler for 'PNM file' 17:33:49: Debug: Adding duplicate image handler for 'PCX file' 17:33:49: Debug: Adding duplicate image handler for 'IFF file' 17:33:49: Debug: Adding duplicate image handler for 'Windows icon file' 17:33:49: Debug: Adding duplicate image handler for 'Windows cursor file' 17:33:49: Debug: Adding duplicate image handler for 'Windows animated cursor file' 17:33:49: Debug: Adding duplicate image handler for 'TGA file' 17:33:49: Debug: Adding duplicate image handler for 'XPM file'
On Windows, these messages are not given, but that is likely a bug in wxWidgets, where no debug messages are given, even though wxWidgets is compiled in debug mode.
The "couldn't set to colour string" messages stem from wxWidgets/src/common/colourcmn.cpp; when the line
wxSafeShowMessage("wxColour::Set - couldn't set to colour string '%s'", str);
is inserted before the debug message, even more colour messages are given on Windows.
The messages might be caused by improper initialization of wxWidgets. See also the bug ticket for wxWidgets
Item | Version |
---|---|
OS | Ubuntu 14.04.1 / Windows 8.1 |
GHC | 7.6.3 / 7.8.3 |
wxWidgets | 3.0.1 |
wxHaskell | 0.91.0.0 |
GCC | 3.4.5 (mingw-vista special r3) |
In Windows, the debug messages become visible when a wxHaskell program is run in the GNU debugger, e.g.:
There is now a solution for the "Debug: Adding duplicate image handler for" messages in the GitHub repository
The "couldn't set to colour string" messages are solved by pull request #19