On Tue Aug 8 09:24:04 2023 +0000, Rémi Bernon wrote:
So far all the windows versions that are checked are following this pattern so it looks reliable to me. I don't understand how we can implement these complex components without having the tests in Wine? For instance how can we implement MF_TOPONODE_WORKQUEUE_ID behavior without this kind of tests?
Tests are of course useful to figure out how it works internally, we can have them as long as they are reliable. Because there is not a lot of reason to chase exact patterns, MFT docs define how these should be used, and internal details do not matter much to us.
Regarding WORKQUEUE_ID, this is interesting in principle, yes. Mostly for the case when branches meet in multi-input MFTs. Otherwise it's probably a matter of returning correct queue id from "IMFAsyncCallback::GetParameters()", could be more complicated. Do we know if something is actually using this attribute?