General idea of this test is to show that a lot of factors influence the fog when transformed and untransformed vertex format was used:
- Directly changing z and w (which is not equal in the corners).
- Changing projection matrix that change z and w.
- Using different programmable/ff vs/ps shader.
- Using different depth bias.
- Chaging depth in pixel shader (oDepth) may or may not affect to colors depending on the vendor implementation.
- And various combinations of above.
This gives `succ` in all cases on this configs:
- Windows 10 with Radeon HD 8400 or Ivy Bridge GT1 (Intel HD Graphics).
- Windows 7 with Radeon HD 6450.
- Windows XP with GeForce Go 7300.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/2657
This is required by https://bugs.winehq.org/show_bug.cgi?id=54660 .
--
v5: vkd3d-shader/hlsl: Consider duplicated input semantic types equivalent in SM1.
vkd3d-shader/hlsl: Handle possibly different types in input semantic var load.
vkd3d-shader/hlsl: Error out when a semantic is used with incompatible types.
vkd3d-shader/hlsl: Error out when an output semantic is used more than once.
vkd3d-shader/hlsl: Support semantics for array types.
vkd3d-shader/hlsl: Don't create semantic vars more than once.
vkd3d-shader/hlsl: Move get_array_size() and get_array_type() to hlsl.c.
tests: Test duplicated semantics.
tests: Test array types with semantics.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/148
User32 uses the input codepage in Unicode edit control.
However, it uses ANSI codepage, i.e. CP_ACP, in ANSI version control.
Comctl32 is different from user32. It doesn't have A-W duality and uses the input codepage in it.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54424
--
v3: comctl32/tests: Add WM_CHAR tests for edit control.
user32/edit: Use CP_ACP for WM_CHAR convresion in ANSI version control.
user32/tests: Fix WM_CHAR tests to use the input codepage.
https://gitlab.winehq.org/wine/wine/-/merge_requests/2173