[PATCH 4/4] d3drm: Implement IDirect3DRMDevice*::Add/DeleteDestroyCallback. (v2)

Stefan Dösinger stefandoesinger at gmail.com
Thu Jul 14 13:50:31 CDT 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 2016-07-11 um 08:46 schrieb Aaryaman Vasishta:
> Umm, It's still not clear whether the interface is QI'd to 
> IDirect3DRMObject or referenced directly. Our implementation
> doesn't do the AddRef, but I don't think refcounting matters much
> in this case, since the callbacks happen right before the object
> gets destroyed.
For the mailing list archives: We talked about this on IRC, and it
turns out that native always passes the version 1 interface to the
callback, regardless of which version was used to call
AddDestroyCallback. (or rather, it passes the IDirect3DRMObject
interface, which happens to share the vtable with the version 1
interface in all objects as far as we know.

Our code already implements this behavior.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXh973AAoJEN0/YqbEcdMwoXEP/24KdStf2VVxBKk62V26TVnw
z8lzY1T6gLR/6ryzOuYAOKjeXRv+ZZgdPyiGhU1jgzXISKy1yAsZIckW5vi+r+2d
niTt++P+/ldoEAxix2Eh4xf0boNjr3VtKVIU14DXpkpOb+VHE6Ldm25Bv0yrhCUm
Ktziod3pqJxVRjDIzFgskyxUyzuVDy7bRKO5JDqOseLh84yVfKFD1Xw1sNW5po/S
30uyUaj6xC04etUd/VAnE9PRiWYWBcGi3hZkVRzJZ8y0dAZQu68ymACP6/5tcT95
FNPhBcOEKB0zDS1kIi5Hv4AaVX9nLSlWlfSZxJJykN8pX564Z62ZZIU3lCq/gJYl
sdp/dC5lmbJxlkk5TtPxS1KsLUk5akm4Ra/t0JbfHBnfqeys0tt8BiJWpcD+Xw1Z
oJ/eqwIbuQw2RsszfcmqWlLJ9LsY8smh5j4PwqS6d0z+SkjQSOyKWlgKyLtb95X+
02HlKWiWn9eGKBVHcox91l0aRvYY6Ho0n4It6tzlG/1HzH0uyyKM/vdWXmkFwCWe
WV0R9jjJB1lKkniVi5FMLQjMGAoDtteNHTMUk+rDFA5tRxqCZiOPvgDarLe70ZaJ
KkfgR9OGlZmjeXdmvAyyn3ckwSWLj2JhGu9bmwuOsRzNs+Ljhfickd7izDubPlqw
4VqTcZqSHLRgTjEF18Bt
=gTtW
-----END PGP SIGNATURE-----



More information about the wine-devel mailing list