Nikolay Sivov writes:
> Ah thanks, so whar<->char is done automatically depending on
> SendMessageA or SendMessageW used?
>
> Next question if you don't mind: IsWindowUnicode() for Wine created
> common controls window handles
> will always return TRUE, so I could easily drop such checks?
I expe
"Nikolay Sivov" wrote:
Next question if you don't mind: IsWindowUnicode() for Wine created
common controls window handles
will always return TRUE, so I could easily drop such checks?
Subclassing a window may change that.
There is a bunch of IsWindowUnicode() tests in dlls/user32/tests/win.c
Alexandre Julliard wrote:
Nikolay Sivov writes:
The question is how could I handle CB_GETLBTEXT properly for ComboEx?
For Combobox it's obvious cause
we know is it unicode or not, for Comboex caller should rely on
IsWindowUnicode() for this control for buffer format or what?
Any thoughts h
Nikolay Sivov writes:
> The question is how could I handle CB_GETLBTEXT properly for ComboEx?
> For Combobox it's obvious cause
> we know is it unicode or not, for Comboex caller should rely on
> IsWindowUnicode() for this control for buffer format or what?
>
> Any thoughts how to deal with this
Is it ok that IsWindowUnicode() returns 1 for windows created with -A calls?
I've just another unrelated issue for Comboex and spotted then I'm
apparently using
unicode window (as reported by this call). But it was created with
---
CreateWindowExA and class WC_COMBOBOXEXA
---
Currently comboex
