Builtin gdiplus behaves as documented but tests are indicating that Windows behaviour sometimes differs from the documentation.
I believe this issue is at least one of the contributing issues to bug https://bugs.winehq.org/show_bug.cgi?id=46947, if not the sole issue. I propose that this flag be disabled until it is well understood. I noticed as issue with DrawString seeming to ignore the flag sometimes(sometimes the text fits without any noticeable defects which I believe is the case with the program in the bug) and sometimes even drawing clipped text with the flag on. Other times it works as expected. I can't seem to find a pattern to identify that could be used to predict its behaviour.
Signed-off-by: David Kahurani k.kahurani(a)gmail.com
--
v5: gdiplus: fix StringFormatFlagsLineLimit handling
https://gitlab.winehq.org/wine/wine/-/merge_requests/3407
This is mostly an attempt to consolidate all the duplicated logic for matching the expected message sequence with the actual message sequence.
Other improvements:
* It seems that winevent_hook_todo wasn't previously reporting cases where Wine correctly sends the event.
* More clarity about which type of message was received when there's a mismatch.
* If a message doesn't match, and does not exist in the expected sequence, only the actual message will be skipped. Otherwise, only the expected message will be skipped. This isn't perfect, but I think it will help make the output from failures more readable.
* Fixed dump_sequence not printing anything for WM_NCCALCSIZE with wParam == FALSE.
Unfortunately, this is going to change the test output, so it will probably break the patterns for testbot detecting known failures. Sorry, Francois.
--
v2: user32/tests: Always generate a description for WM_NCCALCSIZE.
user32/tests: Distinguish between extra and missing messages.
user32/tests: Share code between ok_sequence and dump_sequence.
user32: Remove some todo's for working tests.
user32/tests: Use winetest context in ok_sequence.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3492
This is mostly an attempt to consolidate all the duplicated logic for matching the expected message sequence with the actual message sequence.
Other improvements:
* It seems that winevent_hook_todo wasn't previously reporting cases where Wine correctly sends the event.
* More clarity about which type of message was received when there's a mismatch.
* If a message doesn't match, and does not exist in the expected sequence, only the actual message will be skipped. Otherwise, only the expected message will be skipped. This isn't perfect, but I think it will help make the output from failures more readable.
* Fixed dump_sequence not printing anything for WM_NCCALCSIZE with wParam == FALSE.
Unfortunately, this is going to change the test output, so it will probably break the patterns for testbot detecting known failures. Sorry, Francois.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3492
I'm not sure how could I test this behavior, right now the test I wrote works but there are times where it doesn't enter into the deadlock.
--
v9: evr: Remove process input handling from streaming thread.
evr: Don't lock presenter allocator when calling NotifyRelease
https://gitlab.winehq.org/wine/wine/-/merge_requests/3319
Needed by Underworld Island (Steam ID: 2150830) to skip videos properly.
--
v4: mfmediaengine: Implement media_engine_GetSeekable().
mfmediaengine/tests: Test IMFMediaEngine::GetSeekable().
https://gitlab.winehq.org/wine/wine/-/merge_requests/3536