On Fri Mar 10 09:14:25 2023 +0000, Florian Will wrote:
I can't reproduce this on a Windows 10 machine I have direct access to, but [Marvin reproduces reliably](https://testbot.winehq.org/JobDetails.pl?Key=130454&s201=1&f201=exe3...) (the line numbers are off compared to this MR, I added a bunch of tracing calls). However, Marvin also reproduces this timeout when using [an almost-unchanged (vs. git master) test](https://testbot.winehq.org/JobDetails.pl?Key=130455&f201=exe32.report#k2...), so it does not appear to be a new failure introduced by this MR. As far as I can tell, this test fails: `test_filename_opendlg(filename_noextW, psi_current, defextW, NULL, 0, filename_noextW);`. It looks like the call to `hr = IFileOpenDialog_Show(pfod, NULL);` never returns? But Marvin's "final screenshot" shows no open dialog, either. The last successful thing the test run does appears to be `br = PostMessageW(dlg_hwnd, WM_COMMAND, IDOK, 0);`, which apparently simulates an "OK" button click in the file open dialog. (~~Google tells me `MAKEWPARAM(IDOK, BN_CLICK)` might be a better second argument, but~~ since the dialog closes according to the Marvin screenshot and it works on my bare-metal Window 10 machine, I'm not sure what's going on?)
Locally reproducible when the current directory when running the test is C:\Users\Public\Documents. Apparently, it's impossible to IFileOpenDialog_SetFolder in that dir, it alwas opens the user's Documents folder instead.