[PATCH v5] comctl32: Implement handling of EM_SETCUEBANNER/EM_GETCUEBANNER messages.
Nikolay Sivov
nsivov at codeweavers.com
Sun Oct 28 06:47:47 CDT 2018
On 10/27/2018 11:10 PM, Sergio Gómez Del Real wrote:
>
>
>>> + case EM_SETCUEBANNER:
>>> + result = EDIT_EM_SetCueBanner(es, (const WCHAR *)lParam);
>>> + break;
>> How did you test wParam flag? It seems to work for me as docs describe.
>>
> I tested writing a sample program on Windows 7, 32-bits. On that same
> OS, I got the same results using ControlSpy (for WPARAM it said it was
> unused). Then I googled a bit and read at a couple of places that
> indeed 'Windows' ignores that flag; it always behaves as if WPARAM is
> 0. That is not enough to conclude that all versions of Windows behave
> the same, of course. What version did you try, and what should we do
> with this OS dependence?
>
>
I tested on Windows 10. You're right, I don't see it in 2k3 SDK, in SDK
10.x they have new macro for this, everything still guarded with XP
version. For our implementation it's enough to have a fixme for now, if
it's not working with Win7. If you can't test on Win10 right away, feel
free to send me your test program.
More information about the wine-devel
mailing list