Re: WineD3D: Do not use the IWineD3DSurface for the cursor
On 27/07/06, Stefan Dösinger <stefan(a)codeweavers.com> wrote:
alternatives are do copy the blitting code into present or to add some hack to prevent the original surface from beeing destroyed. What about simply creating a new surface and copying the original surface's contents?
Am Donnerstag 27 Juli 2006 15:59 schrieb H. Verbeet:
about simply creating a new surface and copying the original surface's contents This would go through the whole surface construction code, a HeapAlloc, and the release code + HeapFree every frame to draw the cursor. If I created the surface when the pointer is set I would still have to do refcounting tricks because the newly created surface normally addrefs the device and creates a circular refcount dependency
participants (2)
-
H. Verbeet -
Stefan Dösinger