July 2023 - wine-gitlab

[PATCH v6 0/6] MR3220: windows.devices.bluetooth: Implement IBluetoothAdapterStatics::GetDeviceSelector().
by Mohamad Al-Jaf (＠maljaf) 04 Jul '23

04 Jul '23

Needed for Revo Scan 5. -- v6: windows.devices.bluetooth: Implement IBluetoothAdapterStatics::GetDeviceSelector(). https://gitlab.winehq.org/wine/wine/-/merge_requests/3220

2 7

[PATCH v5 0/6] MR3220: windows.devices.bluetooth: Partially implement IBluetoothAdapterStatics::GetDeviceSelector().
by Mohamad Al-Jaf (＠maljaf) 04 Jul '23

04 Jul '23

Needed for Revo Scan 5. -- v5: windows.devices.bluetooth: Partially implement IBluetoothAdapterStatics::GetDeviceSelector(). windows.devices.bluetooth/tests: Add IBluetoothAdapterStatics::GetDeviceSelector() tests. windows.devices.bluetooth: Add IBluetoothAdapterStatics stub interface. windows.devices.bluetooth: Add stub DLL. include: Add windows.devices.bluetooth.idl file. https://gitlab.winehq.org/wine/wine/-/merge_requests/3220

3 10

[PATCH 0/4] MR263: vkd3d-shader/spirv: Refactor the type system.
by Conor McCarthy (＠cmccarthy) 04 Jul '23

04 Jul '23

Shader Model 6 introduces a 16-bit float (half) type, and 16-bit and 64-bit integer types. Storing extra info in the type enum simplifies checking if a type is any integer, floating point or numeric type, and the declaration of SPIR-V types. The benefits depend on using enum vkd3d_data_type in the backend instead of vkd3d_shader_component_type. Patch 2 is difficult to split because types typically flow through to vkd3d_spirv_get_type_id(), so partial changes would require new calls to conversion functions which would be deleted again later. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/263

2 4

[PATCH v3 0/1] MR3114: comctl32: Make the correct linkid from fun SYSLINK_LinkAtPt.
by Zhao Yi (＠Zhaoyi) 04 Jul '23

04 Jul '23

Add a check condition for whether the type is slLink. Signed-off-by: Zhaoyi <zhaoyi(a)uniontech.com> -- v3: comctl32: Make the correct linkid from fun SYSLINK_LinkAtPt. https://gitlab.winehq.org/wine/wine/-/merge_requests/3114

3 4

Re: [PATCH v3 0/6] MR3165: dxgi: Introduce a worker thread for each D3D12 swapchain (first part).
by Zhiyi Zhang (＠zhiyi) 04 Jul '23

04 Jul '23

On Mon Jul 3 18:50:55 2023 +0000, Zebediah Figura wrote: > > With this implementation it should be relatively easy to present with > whatever API is available, though I don't really know how the options > you mention work, so maybe there is some additional complexity I'm not > aware of. > Sounds great :-) > The "fullscreen window styles" problem (and one of the older d3d > contributors can correct me on this) is basically that some applications > use ddraw (and other versions?) to present to a fullscreen window, > expecting the presented area to cover the whole screen, but wgl (and > Vulkan) swapchains only present to the client rect. We currently get > around this by changing the window styles to remove all the nonclient > decorations, but that breaks some applications too. What we want is a > way to present to the actual window, and part of the idea is that using > D3DKMTPresent() is the architecturally correct way to do this. > I don't quite know what the concerns are for dcomposition either. Zhiyi > was looking at that and ran into a wall, but he probably can at least > describe the problem in greater detail. > There are also some thoughts about using D3DKMTPresent() to deal more > efficiently with some cases where we currently have to do a GDI blit. > I'm fuzzy on these details though; again Henri can explain it better. What D3DKMTPresent() does is that it sends a command to the compositor/DWM to display contents. Since DWM is responsible for drawing the window decoration, it allows the nonclient decorations to be overwritten without affecting window styles. The complexity here is that we don't have a DWM. Implementing a DWM and making it work with the host WM is not trivial, if not impossible. Also, the window decoration is currently handled by the host system, for example, Mutter. Having D3DKMTPresent() is certainly more architecturally correct. That way, DWM can intercept these surfaces and do the composition without tearing and not worry about the surface lifetime. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3165#note_37742

1 0

[PATCH 0/71] MR3168: Draft: Release 8.0.2.
by Michael Stefaniuc (＠mstefani) 04 Jul '23

04 Jul '23

-- This merge request has too many patches to be relayed via email. Please visit the URL below to see the contents of the merge request. https://gitlab.winehq.org/wine/wine/-/merge_requests/3168

3 3

Re: [PATCH v10 0/2] MR3074: Move getpeername() implementation to wineserver
by Chip Davis (＠cdavis5e) 04 Jul '23

04 Jul '23

Typically, `todo_wine` is removed in the commit that fixes the behavior of the underlying API function. (This may be the reason your change hasn't been merged yet.) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3074#note_37738

1 0

[PATCH 0/2] MR3232: d3d10core/tests: Mark test failures specific to the Vulkan or GL renderers.
by Zebediah Figura (＠zfigura) 04 Jul '23

04 Jul '23

This is obviously questionable, as it requires reaching into Wine internals in tests (beyond simply detecting whether Wine is in use). However, we are at a point where, for d3d10 and above, the Vulkan renderer works well enough in general to see real use [in fact, in my experience it usually works better than the GL renderer], and at this point I think avoiding regressions is quite important. It is currently difficult to run tests with it when the results contain so much noise, and I think we need to solve this problem, by actually marking which tests work on each backend. We could in theory expose the renderer through some adapter string, but I believe in the past applications have been sensitive about the contents of adapter strings. Fixing either renderer to reach and maintain parity is not feasible. The GL renderer is not going away, but regrettably GL as an API is abandoned by Khronos, and important features we need in order to implement some Direct3D features will probably never be introduced into GL. Moreover, the amount of effort that would be required to reach parity is not small, and itself would all need to be verified manually. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3232

3 3

[PATCH 0/6] MR259: vkd3d-shader/dxil: Read the DXIL module.
by Conor McCarthy (＠cmccarthy) 04 Jul '23

04 Jul '23

-- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/259

3 24

Re: [PATCH v3 0/6] MR3165: dxgi: Introduce a worker thread for each D3D12 swapchain (first part). - approved
by Zebediah Figura (＠zfigura) 03 Jul '23

03 Jul '23

This merge request was approved by Zebediah Figura. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3165

1 0

2025

2024

2023

2022

wine-gitlab July 2023