I think the problem is that under W2K WinAmp reports the dialog as being ANSI, and under wine it's reported as Unicode (because it's registered using CreateWindowExW with a unicode window proc).
I know in November Dimi was having fun with this sort of thing, and that in Windows the listview at any rate reports this kind of thing incorrectly. Dimi, do you have any tips?
Hopefully later I'll be able to trace it using the MS logger and find out why it thinks it's actually an ansi window.
On Mon, 2003-03-17 at 09:46, Mike Hearn wrote:
On Sun, 2003-03-16 at 23:09, Dmitry Timoshkov wrote:
"Mike Hearn" mike@theoretic.com wrote:
ChangeLog:
- Make the change notifications respect unicode vs ansi.
- TVN_SELCHANGINGW,
- infoPtr->bNtfUnicode ? TVN_SELCHANGINGA : TVN_SELCHANGINGW,
Shouldn't this be reversed?
I was wondering about that when I looked at the code again after coming back to it a few hours later, but the other way around doesn't work properly. I expect bNtfUnicode isn't being set right. I'll take a look today. But that way around is definately the one that makes things work.