Testing shows that this is what native does.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54663

Also add a few more so the full set of callbacks is tested.

Fixes: 2203a856
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54657

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

uiautomationcore: Add support for element array properties in IUIAutomationElement::GetCurrentPropertyValueEx.
Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Connor McAdams <cmcadams@codeweavers.com>

Signed-off-by: Fan WenJie <fanwj@mail.ustc.edu.cn>

Signed-off-by: Fan WenJie <fanwj@mail.ustc.edu.cn>

I am still deliberately not testing after which message the swapchain
state changes from the old state to the new until we find a game that
depends on this.

ddraw, d3d8 and d3d9 do not catch recursive SetDisplayMode or Reset()
calls. They will recurse for about 16 times and then return library
specific weird return values like 0xd0000510 (NTSTATUS, but
nonexistent facility) or 0x88760868 (non-existent HRESULT facility). I
suspect it aborts when the kernel-side message processing stack is
exhausted. As such, an application depending on nested calls in those
libraries would have to deliberately do it, but limit the amount of
nesting to a non-zero amount.

Otherwise a second thread might set it to something else between the
unlock and assignment.

Signed-off-by: Stefan Dösinger <stefan@codeweavers.com>