This format is used by many Unity games, with D3D-enabled source reader.
--
v4: mfreadwrite/reader: Fixup MFVideoFormat_ABGR32 subtype to enumerate the video processor.
winegstreamer: Support MFVideoFormat_ABGR32 output in the video processor.
mfreadwrite/tests: Add tests with MFVideoFormat_ABGR32 output format.
mf/tests: Add video processor tests with MFVideoFormat_ABGR32 format.
mfplat: Add MFVideoFormat_ABGR32 format information.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5626
On Thu May 16 13:27:46 2024 +0000, eric pouech wrote:
> I see your point. Note that the other way around (pseudo "datatypes" for
> function in template argument list) is not correctly detected either
> (eg. in `"?AU?$my_iter@H$0A@Z@@"`)
> and goes down to demangle_datatype
> so I think we should be symmetrical between functions' arg list and
> template arg list
> and hence:
> - move out of demangle_datatype non real data types ($$V as you did, Z
> for ...)
> - handle the end of list cases before calling demangle_datatype
> something like this could do [err](/uploads/314e62b635f2bfcfce46544ac03aaef1/err)
> (not ready for inclusion yet: we don't have test for generating template
> arg list as '<>')
Yes, I think it's better to also move Z and X handling out of demangle_datatype.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/5646#note_70684