The failed 32bit tests are the following:
```
domdoc.c:2521: Test failed: Unexpected hr 0x1.
filtergraph.c:635: Test failed: Got hr 0x40242.
filtergraph.c:571: Test failed: Got hr 0x80004005.
speech.c:1386: Test failed: Wait for block_thread failed.
```
Unrelated to the patch + they've been failing all across different MRs here.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4065#note_48346
On Wed Oct 11 11:05:32 2023 +0000, Chip Davis wrote:
> According to [docs][1], `SetBrushOrgEx()` is supposed to affect the
> *next* brush that is selected into the device context. It might be
> interesting, then, to see what happens when a brush is selected into the
> DC after calling `SetBrushOrgEx()`.
> [1]: https://learn.microsoft.com/en-us/windows/win32/api/wingdi/nf-wingdi-setbru…
That's not reflected by EMF recording, and will need some rendering tests. It's best to have a bug report for that so it's not forgotten.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4058#note_48338
First part of the continuation of the implementation of non-constant offset dereferences (a.k.a. relative addressing) for SM4, now that we use vsir registers in tpf.c.
As a quick recap: while parsing HLSL we are expressing derefs as paths, and then we are lowering these paths into a single offset node (which is closer to the bytecode) using the replace_deref_path_with_offset() pass, right before register allocation.
This first part of the series splits this offset node into 2 parts:
- A constant uint, which will be called hlsl_deref.offset_const.
- A non-hlsl_ir_constant offset node that will only be present when we need relative addressing, that we will end up calling hlsl_deref.offset_rel.
Both these fields will be analog to the ones used in vsir register indexes, vkd3d_shader_register_index.rel_addr and vkd3d_shader_src_param.offset respectively, which is something we need for the second part of this series.
The following patches are in my [nonconst-offsets-8-part](https://gitlab.winehq.org/fcasas/vkd3d/-/commits/n… branch, if something is not clear in this series, it may be worth skimming through them.
Supersedes !229.
--
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/396
Which may be different from the last desktop cursor handle.
This makes the behavior better match the old winex11 behavior, which queried
the current thread input cursor handle on every mouse move to sync it with X11,
although it contradicts MSDN documentation which states that the cursor handle
is global.
This fixes the X11 cursor being visible in "Deus Ex: GOTY Edition".
--
v3: server: Send WM_WINE_SETCURSOR with the thread input cursor handle.
https://gitlab.winehq.org/wine/wine/-/merge_requests/4068