http://bugs.winehq.org/show_bug.cgi?id=7512
------- Additional Comments From dmda@yandex.ru 2007-13-07 11:53 ------- Sure I'll give it a try on the next week. May I ask you why the fix concerns the WndProc only? I thought that if a UNICODE API function is called, regardles the control is ANSI or UNICODE, it still should accept WIDE strings in the INPUT parameters and return WIDE strings in the OUTPUT ones. What I see in 0.9.40 is that UNICODE control treat INPUT as ANSI even if UNICODE function is called. Well, even if control has ANSI WndProc, it should convert UNICODE->ANSI for the parameter I passed to SetWindowTextW. Will the patch fix this problem?