http://bugs.winehq.org/show_bug.cgi?id=23245
--- Comment #21 from Todd Chester ToddAndMargo@gmail.com 2010-07-12 10:39:12 --- (In reply to comment #20)
(In reply to comment #19)
(In reply to comment #17)
Closing - broken environment.
What do you mean? What interaction are you speaking of and what does it have to do with Comctl32? I am confused.
You were using native (Microsoft's) comctl32, which apparently does not play nice with Wine's winecfg. We can't fix their comctl32, and since it works with Wine's, the bug is invalid.
Hi Austin,
Thank you for the explanation.
Winecfg use to work under M$'s conctl32 and then stopped at rc2. My concern was that to get winecfg to work correctly (switching to Wine's conctl32), that programs that require M$'s conctl32 to operate correctly would be broken. I obviously had configured my conctl32 for M$s' version for some reason ages ago that I have forgotten. Since winecfg "used" to operate under both, it would be better to keep it that way.
If you can find no current reason why anyone would ever need to run M$'s conctl32, then my concerns are unfounded. If my concerns are founded, please reopen this bug and fix winecfg.
Many thanks, -T