May 2018 - Wine-Devel - list.winehq.org

Re: [PATCH 6/8] dxgi/tests: Use global memory allocation helpers.

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH 8/8] dxgi/tests: Add option to use selected adapter.

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH 7/8] dxgi/tests: Add test for creating swapchains with multisampling.

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH 5/8] dxgi/tests: Handle DXGI_ERROR_NOT_CURRENTLY_AVAILABLE in test_fullscreen_resize_target().

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH resend 3/8] dxgi: Implement d3d12_swapchain_GetCurrentBackBufferIndex().

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH resend 4/8] dxgi: Implement d3d12_swapchain_Present1().

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH resend 2/8] dxgi: Implement d3d12_swapchain_GetBuffer().

by Henri Verbeet

Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>

May 31, 2018

Re: [PATCH] winex11.drv: Request _NET_ACTIVE_WINDOW in SetFocus().

by Zebediah Figura

On 05/31/2018 10:10 AM, Dmitry Timoshkov wrote: > Zebediah Figura <zfigura(a)codeweavers.com> wrote: > >>> New version of the patch still doesn't work here, same flickering in an >>> infinite loop until I move mouse over the test's window. >>> >> >> Thanks. It looks like Marco sends a WM_TAKE_FOCUS message when honouring >> a request to become the active window. Since we call >> SetForegroundWindow() inside of our WM_TAKE_FOCUS handler, we generate a >> loop. This wouldn't be a problem, except that the application creates >> two windows in quick succession before processing events, and Marco >> generates one WM_TAKE_FOCUS message for each, so we essentially start >> out one WM_TAKE_FOCUS message behind the most recent one. >> >> It's not clear to me what we should do about this; the spec doesn't seem >> to explicitly forbid any of this behaviour, but neither does it say we >> can depend on receiving WM_TAKE_FOCUS in response to a >> _NET_ACTIVE_WINDOW request. Could someone more knowledgeable about X11 >> provide input? > > Does the original version of the patch work for you? What is the reason > of the changes you've made in the staged patch? > It seems unnecessary to add a new driver function for SetActiveWindow. All three focus functions have the effect of raising/activating the window in the same way that _NET_ACTIVE_WINDOW does, and the Mac driver already activates and raises windows in its SetFocus() handler.

May 31, 2018

[PATCH] ntdll: Partly implement RtlDosPathNameToRelativeNtPathName_U_WithStatus (resend 2nd)

by Stefan Leichter

Re-diffed/send with some (more) blanks in the subject Signed-off-by: Stefan Leichter <sle85276(a)gmx.de> --- dlls/ntdll/ntdll.spec | 1 + dlls/ntdll/ntdll_misc.h | 6 ++++++ dlls/ntdll/path.c | 21 +++++++++++++++++++++ 3 files changed, 28 insertions(+)

May 31, 2018

Re: [PATCH] winex11.drv: Request _NET_ACTIVE_WINDOW in SetFocus().

by Dmitry Timoshkov

Zebediah Figura <zfigura(a)codeweavers.com> wrote: > > New version of the patch still doesn't work here, same flickering in an > > infinite loop until I move mouse over the test's window. > > > > Thanks. It looks like Marco sends a WM_TAKE_FOCUS message when honouring > a request to become the active window. Since we call > SetForegroundWindow() inside of our WM_TAKE_FOCUS handler, we generate a > loop. This wouldn't be a problem, except that the application creates > two windows in quick succession before processing events, and Marco > generates one WM_TAKE_FOCUS message for each, so we essentially start > out one WM_TAKE_FOCUS message behind the most recent one. > > It's not clear to me what we should do about this; the spec doesn't seem > to explicitly forbid any of this behaviour, but neither does it say we > can depend on receiving WM_TAKE_FOCUS in response to a > _NET_ACTIVE_WINDOW request. Could someone more knowledgeable about X11 > provide input? Does the original version of the patch work for you? What is the reason of the changes you've made in the staged patch? -- Dmitry.

May 31, 2018