FWIW, as far as I'm concerned, this or a similar patch should probably still be merged, to fix the wow64 stub. It basically just comes down to the approach to fix it. If anyone gets a chance to look at this let me know.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6584#note_86467
This fixes one of the regression with ShellExecute when using a full patch and an executable without an extension.
--
v4: shell32: Allow FindExecutables to find unix files.
https://gitlab.winehq.org/wine/wine/-/merge_requests/6285
On Sat Nov 2 08:52:23 2024 +0000, Zhiyi Zhang wrote:
> This `else` branch should never get executed because only the
> test_WM_NOTIFY() test sends a WM_NOTIFY with TEST_WM_NOTIFY_CODE. So you
> can delete this branch.
`else` branch will be executed if WM_NOTIFY message gets forwarded twice by buggy non-test code
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6737#note_86464
Zhiyi Zhang (@zhiyi) commented about dlls/comctl32/tests/toolbar.c:
>
> return 0;
> }
> + case TEST_WM_NOTIFY_CODE:
> + if (expecting_test_WM_NOTIFY)
> + {
> + ok(hdr == &test_WM_NOTIFY_nmhdr, "Got unexpected header.\n");
> + ok(wParam == TEST_WM_NOTIFY_IDFROM, "Got unexpected wParam 0x%Ix.\n", wParam);
> + }
> + else
This `else` branch should never get executed because only the test_WM_NOTIFY() test sends a WM_NOTIFY with TEST_WM_NOTIFY_CODE. So you can delete this branch.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6737#note_86459