- Wine-gitlab - list.winehq.org

[PATCH v6 0/2] MR231: SetWindowPos() parent window exposure fixes (#53153)
by Jinoh Kang (＠iamahuman) 26 Oct '22

26 Oct '22

Signed-off-by: Jinoh Kang <jinoh.kang.kr(a)gmail.com> -- v6: https://gitlab.winehq.org/wine/wine/-/merge_requests/231

3 4

[PATCH v2 0/4] MR1157: win32u: Move DisplayConfigGetDeviceInfo from user32 and implement DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME.
by Paul Gofman (＠gofman) 26 Oct '22

26 Oct '22

-- v2: win32u: Implement NtUserDisplayConfigGetDeviceInfo(DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME). win32u: Store output id in monitors cache. https://gitlab.winehq.org/wine/wine/-/merge_requests/1157

5 8

[PATCH v2 0/9] MR36: hlsl: UAV loads and stores.
by Zebediah Figura (＠zfigura) 26 Oct '22

26 Oct '22

-- v2: vkd3d-shader/hlsl: Propagate copies for resource store instructions. vkd3d-shader/hlsl: Write SM4 UAV store instructions. vkd3d-shader/hlsl: Parse UAV stores. vkd3d-shader/hlsl: Implement typed UAV loads. vkd3d-shader/hlsl: Write SM4 UAV declarations. vkd3d-shader/hlsl: Allocate UAVs. tests: Add a test for storing to a UAV array. tests: Add more tests for UAV allocation. tests: Fix constructor declaration in the partial UAV write test. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/36

5 16

[PATCH 0/3] MR40: vkd3d-shader/hlsl: Support complex implicit casts, complex explicit casts and complex broadcasts. (PART 3/3)
by Francisco Casas (＠fcasas) 26 Oct '22

26 Oct '22

Just additional complex explicit casts tests. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/40

5 6

Re: [PATCH v5 0/4] MR1159: msvcrt: add implementation for localized functions - approved
by Piotr Caban (＠piotr) 26 Oct '22

26 Oct '22

This merge request was approved by Piotr Caban. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1159

1 0

[PATCH 0/3] MR566: shell32: Implement SHBindToFolderIDListParent.
by Mohamad Al-Jaf (＠maljaf) 26 Oct '22

26 Oct '22

Called by IE11. Signed-off-by: Mohamad Al-Jaf <mohamadaljaf(a)gmail.com> v3: Fix failed test. Don't know how to change the subject version number. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/566

4 7

[PATCH v5 0/3] MR231: SetWindowPos() parent window exposure fixes (#53153)
by Jinoh Kang (＠iamahuman) 26 Oct '22

26 Oct '22

Signed-off-by: Jinoh Kang <jinoh.kang.kr(a)gmail.com> -- v5: server: Don't invalidate the newly exposed child region on the parent if it doesn't clip children. server: Redraw composited window child when its z-order changes. server: Correctly expose composited parent window and its child on position change. https://gitlab.winehq.org/wine/wine/-/merge_requests/231

3 4

[PATCH 0/1] MR1169: conhost/tests: Fix some conditions on tty test termination.
by eric pouech (＠epo) 26 Oct '22

26 Oct '22

Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1169

2 1

Re: [PATCH v6 0/2] MR979: d3d9: Implement d3dx_effect_SetRawValue
by Matteo Bruni (＠Mystral) 26 Oct '22

26 Oct '22

On Wed Oct 19 09:55:18 2022 +0000, Patrick Hibbs wrote: > The same issue with strings occurs with Texture and shader types. > I.e. Paramater is rendered irretrievable. Calling it's relevant GetXXX() > function causes a crash if it's a scalar. Calling GetParamaterByName() > will return an invalid handle. Oh, interesting. GetParameterByName() failing afterwards is probably an indication that the SetRawValue() call overwrote parts of some internal data structure and broke the effect object to some degree. BTW, you're supposed to set texture parameters to a IDirect3DBaseTexture9 / IUnknown pointer (and similarly the value for a string parameter should probably be a string pointer rather than the string contents). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/979#note_12212

1 0

Re: [PATCH v6 0/2] MR979: d3d9: Implement d3dx_effect_SetRawValue
by Matteo Bruni (＠Mystral) 26 Oct '22

26 Oct '22

On Wed Oct 19 11:26:44 2022 +0000, Patrick Hibbs wrote: > Done in v3 of the patch. > Should I respond to all of these if I think it's been done? > Should I mark the thread resolved if I think it's been done, or is that > something the reviewer should do? Feel free to mark the threads that you think are done with as resolved (I think I can still reopen them if I happen to disagree) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/979#note_12213

1 0