- Wine-GitLab - list.winehq.org

[PATCH v2 0/1] MR2232: msado15: Semi-stub _Recordset get/put Filter
by Alistair Leslie-Hughes (＠alesliehughes) Feb. 19, 2023

Feb. 19, 2023

-- v2: msado15: Semi-stub _Recordset get/put Filter https://gitlab.winehq.org/wine/wine/-/merge_requests/2232

2 1

[PATCH 0/1] MR2232: msado15: Semi-stub _Recordset get/put Filter
by Alistair Leslie-Hughes (＠alesliehughes) Feb. 19, 2023

Feb. 19, 2023

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/2232

3 2

[PATCH v2 0/4] MR89: vkd3d-shader/hlsl: Improve support for logarithmic functions.
by Nikolay Sivov (＠nsivov) Feb. 18, 2023

Feb. 18, 2023

-- v2: vkd3d-shader/hlsl: Support log() intrinsic. vkd3d-shader/hlsl: Support log10() intrinsic. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/89

3 10

[PATCH v4 0/1] MR2229: winex11: Fix X11 WM behavior for Delphi based apps.
by Roberto Fernandez (＠rfz) Feb. 18, 2023

Feb. 18, 2023

Fixes the longstanding misbehavior of X window managers with respect to Delphi based applications. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=26503 -- v4: winex11: Fix X11 WM behavior for Delphi based apps. https://gitlab.winehq.org/wine/wine/-/merge_requests/2229

2 1

[PATCH v3 0/4] MR2229: winex11: Fix X11 WM behavior for Delphi based apps.
by Roberto Fernandez (＠rfz) Feb. 18, 2023

Feb. 18, 2023

Fixes the longstanding misbehavior of X window managers with respect to Delphi based applications. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=26503 -- v3: winex11: Fix X11 WM behavior for Delphi based apps. Revert "winex11: add missing newline in TRACE." winex11: add missing newline in TRACE. winex11: Fix X11 WM behavior for Delphi based apps. https://gitlab.winehq.org/wine/wine/-/merge_requests/2229

3 6

[PATCH v2 0/4] MR2225: uiautomationcore: Initial COM IUIAutomation API patches.
by Connor McAdams (＠cmcadams) Feb. 18, 2023

Feb. 18, 2023

-- v2: uiautomationcore: Implement IUIAutomationElement::GetCurrentPropertyValueEx. uiautomationcore: Implement IUIAutomation::ElementFromHandle. uiautomationcore: Add stub IUIAutomation implementation. https://gitlab.winehq.org/wine/wine/-/merge_requests/2225

3 6

Re: [PATCH v2 0/1] MR2229: winex11: Fix X11 WM behavior for Delphi based apps.
by Bernhard Kölbl Feb. 18, 2023

Feb. 18, 2023

Bernhard Kölbl (@besentv) commented about dlls/winex11.drv/event.c: > if (hwnd) hwnd = NtUserGetAncestor( hwnd, GA_ROOT ); > if (!hwnd) hwnd = get_active_window(); > if (!hwnd) hwnd = last_focus; > - if (hwnd && can_activate_window(hwnd)) set_focus( event->display, hwnd, event_time ); > + if (hwnd && can_activate_window(hwnd)) > + { > + Window win = X11DRV_get_whole_window(hwnd); > + if (win) > + { > + TRACE("will raise window %p", hwnd); Missing a newline here. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2229#note_24740

1 0

[PATCH 0/3] MR2224: include: Add dcomp.h.
by Zhiyi Zhang (＠zhiyi) Feb. 18, 2023

Feb. 18, 2023

Note that there are some C++ methods of IDCompositionVisual are renamed to avoid conflicts. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2224

4 8

[PATCH v3 0/2] MR2215: winsock: Fix two connect() issues.
by Paul Gofman (＠gofman) Feb. 18, 2023

Feb. 18, 2023

I was mainly after the issue fixed by the second patch but stomped on another one while testing that and that one looks even more unfortunate to me. 1. When connect() is used on blocking socket and fails for whatever reason, next connect() will make a new independent connection attempt (both on Windows and Unix). In non-blocking mode however (and Unix sockets are always in non-blocking mode in Wine) on Linux the next connect() will always return an error (unlike Windows which will make a new connect attempt if the previous one completed and failed). So in Wine now even for blocking socket connect() will fail if previous attempt failed and return WSAECONNABORTED. The error returned by Linux connect() will be ECONNABORTED if getsockopt(SO_ERROR) was called on the socket after connect completed with failure, and true connect() fail error if getsockopt wasn't called. 2. connect() on blocking socket times out after ~21sec on Windows and after ~130 sec on Linux. That is the case when peer doesn't actively reject connection but just never replies anything. That is, client sent SYN and never heard back. So much longer timeout leads to what is seen as hang on exit in one game, but probably more important that it affect much more in various apps provoking timeouts or huge delays not just on exit. I did not find a way to set connect() timeout for socket on Windows. That difference mostly corresponds to number of SYN send retries. That is 7 on Linux by default and 4 on Windows (the delay between attempts starts from 1s and is doubled on each next attempt). There is TCP_SYNCNT socket option (Linux specific now, unfortunately) which allows to set the number of retries. Setting that to 4 yields 32 sec timeout (vs 21 sec on Windows). The remaining difference is probably due to different amount of time waited after last SYN is sent. There is also TCP_USER_TIMEOUT parameter which allows to effectively set the delay exactly, but it might interfere with SO_KEEPALIVE somehow and I hope that 32 vs 21 is not that critical already as 130 vs 21 and probably we can avoid complicating the thing with it. -- v3: server: Set TCP SYN count on sockets. server: Retry socket connection on ECONNABORTED error. https://gitlab.winehq.org/wine/wine/-/merge_requests/2215

2 3

[PATCH v2 0/2] MR2215: winsock: Fix two connect() issues.
by Paul Gofman (＠gofman) Feb. 18, 2023

Feb. 18, 2023

I was mainly after the issue fixed by the second patch but stomped on another one while testing that and that one looks even more unfortunate to me. 1. When connect() is used on blocking socket and fails for whatever reason, next connect() will make a new independent connection attempt (both on Windows and Unix). In non-blocking mode however (and Unix sockets are always in non-blocking mode in Wine) on Linux the next connect() will always return an error (unlike Windows which will make a new connect attempt if the previous one completed and failed). So in Wine now even for blocking socket connect() will fail if previous attempt failed and return WSAECONNABORTED. The error returned by Linux connect() will be ECONNABORTED if getsockopt(SO_ERROR) was called on the socket after connect completed with failure, and true connect() fail error if getsockopt wasn't called. 2. connect() on blocking socket times out after ~21sec on Windows and after ~130 sec on Linux. That is the case when peer doesn't actively reject connection but just never replies anything. That is, client sent SYN and never heard back. So much longer timeout leads to what is seen as hang on exit in one game, but probably more important that it affect much more in various apps provoking timeouts or huge delays not just on exit. I did not find a way to set connect() timeout for socket on Windows. That difference mostly corresponds to number of SYN send retries. That is 7 on Linux by default and 4 on Windows (the delay between attempts starts from 1s and is doubled on each next attempt). There is TCP_SYNCNT socket option (Linux specific now, unfortunately) which allows to set the number of retries. Setting that to 4 yields 32 sec timeout (vs 21 sec on Windows). The remaining difference is probably due to different amount of time waited after last SYN is sent. There is also TCP_USER_TIMEOUT parameter which allows to effectively set the delay exactly, but it might interfere with SO_KEEPALIVE somehow and I hope that 32 vs 21 is not that critical already as 130 vs 21 and probably we can avoid complicating the thing with it. -- v2: server: Set TCP SYN count on sockets. server: Retry socket connection on ECONNABORTED error. https://gitlab.winehq.org/wine/wine/-/merge_requests/2215

3 4