GNOME Bugzilla – Bug 519410
drawing error with win32 theme for file-type combo
Last modified: 2008-03-12 23:41:18 UTC
SaveAs dialog with a file type combo is putting a white background behind the combo label that goes away when a redraw is forced.
Created attachment 106197 [details] screenshot of the oddness. Full debuggable installation package available from http://www.gnome.org/~jody/gnumeric/win32/gnumeric-1.9.0-win32-1.exe It's not impossible this is specific to my cross compiled build. Any ideas ?
It seems like I saw something like this quite awhile ago in gtk-demo under the "Combo boxes" demo, but I thought it has been gone for awhile now. What version of gtk+ are you using, or is this very recent svn?
libgtk-win32-2.0-0.dll File version: 2.12.8.0
This happens with the "XP" theme.
Tidbit - this happens on gtk-demo with Jody's version of GTK+, but not on gtk-demo using Pidgin 2.4.0's version of GTK+. Both are allegedly GTK+ 2.12.8.0. The problem goes away if you copy Pidgin's copy of the ms-windows theme engine (libwimp.dll) to Gnumeric.
There is a sample package in http://www.gnome.org/~jody/gnumeric/win32/gnumeric-1.9.0-win32-20080301.exe with all libraries built with -g -O0 It's possible that the lack of optimization is what is triggering this.
How would the optimizations, or lack thereof, affect this? That seems kind of unlikely doesn't it? I can try to build both ways just to test, though.
optimzation or lack thereof sometimes uncovers the use of uninitialized memory. The usual symptom is things working in a development build because the uninitialized memory is more likely to be 0.
*** Bug 503794 has been marked as a duplicate of this bug. ***
I noticed an identical display error in gtk-demo's "Combo Boxes" with a libgobject DLL (!) compiled (with debugging) with MSVC6. With a libgobject DLL compiled (also with debugging) with gcc, no glitch. Nothing else changing. (This is with trunk GLib and GTK+.) Extremely weird...
This probably is a dupe of bug #461805, which arc just has been fixing, isn't it?
The patch in 461805 solves the problem. *** This bug has been marked as a duplicate of 461805 ***