- 05 Aug, 2021 10 commits
-
-
Alex Henrie authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=50419Signed-off-by:
Alex Henrie <alexhenrie24@gmail.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Alex Henrie authored
Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Alex Henrie authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51469Signed-off-by:
-
Francois Gouget authored
GetLocaleInfoW() already caches the registry information and is fast enough. This also avoids using out-of-date information after a SetLocaleInfoW() call. Signed-off-by:
Francois Gouget <fgouget@codeweavers.com> Signed-off-by:
-
Hugh McMaster authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=50187Signed-off-by:
Hugh McMaster <hugh.mcmaster@outlook.com> Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Arkadiusz Hiler authored
Both Acquire() and event processing with DirectInput seem to be asynchronous. In most cases we can just keep hammering GetDeviceData() until the event gets processed. Things get pretty racy around Acquire() though. If we fire event right after the device is acquired we can find ourselves in one of the three situations: 1. Event happened after acquiring has completed - the wait will suffice. 2. Event happened before acquiring did any real work - the device will pick up the state as if the event was processed, but there's nothing in GetDeviceData(). Because of that we cannot fail on wait. 3. Event happened somewhere in the middle of acquiring - we ended up both missing the event for GetDeviceData() and we have outdated state. Sending event again will register as if the button was not already pressed. This change covers all three scenarios. Signed-off-by:
Arkadiusz Hiler <ahiler@codeweavers.com> Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Paul Gofman authored
Signed-off-by:
Paul Gofman <pgofman@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
- 04 Aug, 2021 30 commits
-
-
Alex Henrie authored
Signed-off-by:
Zebediah Figura <zfigura@codeweavers.com> Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Alex Henrie authored
Namely IPV6_HOPLIMIT and IPV6_PKTINFO. Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Austin English authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51374Signed-off-by:
Austin English <austinenglish@gmail.com> Signed-off-by:
-
Gabriel Ivăncescu authored
Names after the first one are supposed to retrieve DISPIDs for parameters, but it doesn't seem to be implemented on Windows. Signed-off-by:
Gabriel Ivăncescu <gabrielopcode@gmail.com> Signed-off-by:
-
Gabriel Ivăncescu authored
Names after the first one are supposed to retrieve DISPIDs for parameters, but it doesn't seem to be implemented on Windows. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Instead of STATUS_BUFFER_TOO_SMALL when input report buffer length is less than InputReportByteLength. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
-
Francois Gouget authored
With some time source drivers the requested timer resolution is rounded to the nearest value supported by the hardware, and that is then reported by NtSetTimerResolution(). So adjust the timer tests to allow close values, including outside the max-min range! Make sure the values given to NtQueryTimerResolution() are well outside the range of what it could return. Signed-off-by:
-
Zebediah Figura authored
This was introduced in 3a5b7cf1 as way to expose wine_call_to_16_regs_long(); however, the same commit changed the only user to use WCB16_REGS instead. Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
Piotr Caban <piotr@codeweavers.com> Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Piotr Caban authored
Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st> Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
Martin Storsjö authored
The x86 style x87/sse split of status bits isn't present on arm64. Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
