Introduces an `idx_count` field to `struct vkd3d_shader_register`. Another patch set is needed for further validations and to use this field where applicable.
--
v5: vkd3d-shader/tpf: Validate input and output index ranges for default control point phases.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/198
Introduces an `idx_count` field to `struct vkd3d_shader_register`. Another patch set is needed for further validations and to use this field where applicable.
--
v4: vkd3d-shader/tpf: Remove an unnecessary carriage return from a parser error message.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/198
This fixes the behavior in notepad, with Japanese ibus-mozc IME, when typing "NIHONGO-SPACE-NO", or with Korean ibus-hangul when typing "GA-NA-DA". The latter still has an issue with the last character not appearing in the a composition but I believe it is unrelated to comctl32 and will be fixed by some future imm32 changes.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/2743
--
v3: tests: Add a test for SampleBias() with multiple mipmap levels.
tests: Add a test for sampling from nonzero mipmap levels.
tests: Add a test for loading from nonzero mipmap levels.
tests/shader_runner: Add support for creating mipmapped textures.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/191
I think this commit is great as it will reduce the maintenance cost of the different `msxml*` dlls by unifying work.
If a version of a different `msxml*` act differently than the other version we can always do something like in `.spec` files:
```
@ stdcall -private DllGetClassObject(ptr ptr ptr) winexml.MSXML*_DllGetClassObject
```
But by checking: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/msvcr120/Makefile.in
Moving all code to `msxml` and using `PARENTSRC` would seems to be more in line with what wine is already doing.
Either way is fine, the only thing that is sure is that splitting xml source work for each dll is not healthy, and code need to be cross merged in some way.
Using a `winexml` is more memory efficient, but using `msxml` + `PARENTSRC` seems more application compatible, either way is fine for me.
Also making `wine*` modules seems to become a recent common trend, see: https://gitlab.winehq.org/wine/wine/-/merge_requests/2298
@julliard I think you should make clearer guidelines about making `wine*.dll` modules, and proposing alternative to these modules in the guidelines.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/2700#note_31956