While I have no clear idea about the cause of the issue, my gut
feeling is that it happens with overloaded functions. In above case:
STDMETHOD(SetOffsetX)(THIS_ float) PURE;
STDMETHOD(SetOffsetX)(THIS_ IDCompositionAnimation*) PURE;
That's right, overloads like that appear in reversed order in actual
vtable. So method with float arg gets higher address.
So, does inverting the declaration order of these methods would do the
tricks?
This is quite surprising to declare member functions in different order
according to the compiler.
Pierre
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
