6 Jan 2006
AbiWord , or Progress mixed with “Isn’t That Strange…”
So as 2.4.2 is prepared for release sometime soon, I found it necessary to reboot over into Windows and do my duty with the compiling. I don’t have a CVS-STABLE tree checked out, so I rely on only gentle changes occuring to stable (which is generally just fine), and in case of some major problem surfacing at a tagging point, we can just fix it and re-tag, since tag comes before release.
So this time, as I’m getting the binaries completed, the notorious “hang during documentation build” occurs, and the matching “cause random processes in Windows to run away with CPU” symptom surfaces. Through some careful priority management, I get the build to run again, and correctly. Alright. Log off, and log back on, time to install. The install works great, and aside from a strange plugin conflict (now resolved with a stop-gap measure), it all looks good.
Well, almost all. For some strange, strange reason, the background color of the drop down boxes on the toolbars (style, font, size, and zoom) is grey, rather than white as expected. It all works fine, but the boxes look almost disabled, even though they aren’t.
I have no idea what caused this, where it came in during development, or how to fix it. I don’t recall it occurring in 2.4.1, but neither do I recall any commits that would affect the Windows front end’s coloring of drop-down boxes. Go figure.
So there’s my mystery. Any ideas?
(Yes, I’ll file a bug next time I boot into Windows.)
PS. I <3 VMWare, and as soon as it’s financial feasible and sensible, I will get Workstation instead of installing Windows on top of an installation of Fedora Core in VMPlayer. Qemu has been officially been blown right out of the metaphorical water.