Advice fixing #13683 (DirectX mouse overlay?)

[Ken Thomases]

On Feb 15, 2014, at 6:17 PM, Christopher Thielen wrote:

> I'm attempting to fix http://bugs.winehq.org/show_bug.cgi?id=13683 but need some advice as to where to start. I'm not too familiar with hacking on Wine.
> 
> I'd like to test Stefan Dösinger's theory outlined in the comments for #13683 that the missing second mouse cursor is perhaps being implemented using DirectX overlays and that Wine's lack of overlay compatibility flags is to blame.
> 
> Would the proper action to test this theory be to fake a certain set of flags in dlls/d3d8/device.c's static HRESULT WINAPI d3d8_device_GetDeviceCaps(IDirect3DDevice8 *iface, D3DCAPS8 *caps) ? If that proves to be the issue, I'd then need to write proper code to report the correct set of flags presumably.

Probably you should start by collecting a log with the +ddraw,+d3d,+d3d_surface channels and looking for messages that mention "overlay".

From a cursory look, it seems that wined3d supports some types of overlay surfaces and some operations on those surfaces, but not all.


> Is there any easy way to see which DLLs Wine loads when running an application?

You can look at a +module log.

-Ken