- 11 Jan, 2023 9 commits
-
-
Hans Leidekker authored
-
Zhiyi Zhang authored
Some window managers have trouble moving fullscreen windows to another monitor. For example, KWin doesn't allow moving windows with _NET_WM_STATE_FULLSCREEN set. FVWM used by TestBots keeps the size for fullscreen windows after they are moved to another monitor and when the window is also fullscreen on the new monitor, which could be a bug in FVWM. But let's work around this in the tests as well. The changed tests don't need created windows being fullscreen at the start. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54172
-
Hans Leidekker authored
-
Hans Leidekker authored
Avoids test failures when the URL is cached by other tests. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51227
-
Alexandre Julliard authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54218
-
Eric Pouech authored
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Eric Pouech authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54287Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Eric Pouech authored
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Hugh McMaster authored
To ensure a seamless transition between value names, we try loading the registry value from FontFamily first and FontPitchFamily second. Any changes to the console font family are saved to the new value name.
-
- 10 Jan, 2023 5 commits
-
-
Alexandre Julliard authored
-
Jacek Caban authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54263
-
Jacek Caban authored
Based on mingw-w64.
-
Paul Gofman authored
-
Stefan Dösinger authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53671
-
- 09 Jan, 2023 11 commits
-
-
Gabriel Ivăncescu authored
SetWindowIcon can pass an icon as a parameter, but in that case NtUserGetIconInfo is never called, so the icon info is never filled. Fixes a regression introduced by 3eb944c0. Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>
-
Eric Pouech authored
There are cases in Windows10+ where the WM_PASTE message doesn't paste the content of the clipboard. This appeared in testing: - almost always just after (for a couple of milliseconds) setting new content into the clipboard and closing it. - in some unrelated rare occasions (like once for 400 runs). It looks like another (installed) process had opened the clipboard and forbids the paste command. As WM_PASTE doesn't return success/error status, workaround it by wrapping the WM_PASTE command into a helper, and retry when the clipboard's content hasn't been pasted. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53276 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53277Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Eric Pouech authored
As the clipboard is a shared resource, we cannot expect that no other app hasn't openeded it. So wrap clipboard access with a retry feature in case of failure. Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Eric Pouech authored
There are cases in Windows10+ where the WM_PASTE message doesn't paste the content of the clipboard. This appeared in testing: - almost always just after (for a couple of milliseconds) setting new content into the clipboard and closing it. - in some unrelated rare occasions (like once for 400 runs). It looks like another (installed) process had opened the clipboard and forbids the paste command. As WM_PASTE doesn't return success/error status, workaround it by wrapping the WM_PASTE command into a helper, and retry when the clipboard's content hasn't been pasted. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53276Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Eric Pouech authored
As the clipboard is a shared resource, we cannot expect that no other app hasn't openeded it. So wrap clipboard access with a retry feature in case of failure. Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
-
Gabriel Ivăncescu authored
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>
-
Hans Leidekker authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52557
-
Zhiyi Zhang authored
Using EnumDisplaySettings() directly to query display depth has a high overhead when using the XRandR 1.0 display device handler on some NVIDIA setups. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51420 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53382
-
Alistair Leslie-Hughes authored
Cherry-picked from upstream commit 16f86bffec36b6e82e5c93d5f04ebc4ee4f980ab. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54264
-
Alexandre Julliard authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53583 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53837
-
Alexandre Julliard authored
-
- 08 Jan, 2023 1 commit
-
-
Alexandre Julliard authored
-
- 07 Jan, 2023 1 commit
-
-
Alexandre Julliard authored
-
- 06 Jan, 2023 13 commits
-
-
Piotr Caban authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54180
-
Piotr Caban authored
-
Philip K. Gisslow authored
The pSignatureSettings field was not unitilized so it got a random value from the stack causing a later crash when it was dereferenced in Wintrust (SoftPubloadSignature).
-
Nikolay Sivov authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54151
-
Vladislav Timonin authored
An improvement of 5f0dcf79, which, depending on theme, had an issue with drawing the top border clipped inside the header.
-
Zhiyi Zhang authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53995
-
Zebediah Figura authored
I was unable to write tests for this; it seems it doesn't consistently work on Windows. However, Rayman 3 seems to rely on it; it maps the same buffer twice immediately after creation, with DISCARD flags on both maps, and expects the same address to be returned. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53752
-
Ziqing Hui authored
-
Ziqing Hui authored
-
Zebediah Figura authored
The code originally intended to achieve this by simply waiting on flushing_cs, and having the application thread hold flushing_cs while seeking. Unfortunately, this can result in starvation of the application thread, since the streaming thread always reacquires flushing_cs immediately after releasing it. Avoid this by using a separate condition variable. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53403Signed-off-by: Zebediah Figura <zfigura@codeweavers.com>
-
Zebediah Figura authored
The code previously relied on inherent atomicity of atomic types, but atomicity doesn't imply the right memory ordering. Be explicit about the threading model we want. Signed-off-by: Zebediah Figura <zfigura@codeweavers.com>
-