[PATCH 1/2] d3drm: Implement IDirect3DRM*::CreateObject.

Aaryaman Vasishta jem456.vasishta at gmail.com
Mon Apr 18 10:45:38 CDT 2016

I thought it'd be a good idea to keep it void * for once future objects
would be implemented (i.e. the one's that have todo marked as true in the
But you do have a point. Since I'm just returning texture objects right
now, maybe using d3drm_texture structure would do. What should I go with?


On Mon, Apr 18, 2016 at 6:58 PM, Henri Verbeet <hverbeet at gmail.com> wrote:

> On 18 April 2016 at 15:15, Aaryaman Vasishta <jem456.vasishta at gmail.com>
> wrote:
> > On Mon, Apr 18, 2016 at 4:17 PM, Henri Verbeet <hverbeet at gmail.com>
> wrote:
> >> Why do you need "object_struct"?
> >
> > I need it to store the object's address, from which the IUnknown
> interface
> > is obtained which in turn is used to QI the required object using iid.
> >
> > Am I missing something? Is there a better way? I suppose I could re-use
> > object and keep it as a void * instead of IUnknown..
> >
> What's wrong with using a d3drm_texture structure?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20160418/dc0aa704/attachment.html>

More information about the wine-devel mailing list