Le 09/05/2013 22:15, Christian Costa a écrit :
Le 09/05/2013 22:05, Alexandre Julliard a écrit :
Christian Costa <titan.co...@gmail.com> writes:
@@ -677,6 +677,7 @@ HRESULT WINAPI D3DXFileCreate(ID3DXFile **d3dxfile)
{
ID3DXFileImpl *object;
HRESULT ret;
+ const char expand_string[] = "expand_string";
TRACE("(%p)\n", d3dxfile);
@@ -701,6 +702,11 @@ HRESULT WINAPI D3DXFileCreate(ID3DXFile
**d3dxfile)
object->ID3DXFile_iface.lpVtbl = &ID3DXFile_Vtbl;
object->ref = 1;
+ /* Enable string expansion extension in d3dxof */
+ ret = IDirectXFile_RegisterTemplates(object->dxfile,
(void*)expand_string, sizeof(expand_string));
+ if (ret != DXFILE_OK)
+ ERR("Native d3dxof.dll used. Use builtin one to avoid
problem.\n");
That's really ugly. You have to find a better way.
The d3dxof extension itself or how it is enabled ?
In latter case. Is adding an extension function "enable_d3dx_mode" to
d3dxof and do a GetProcAddress on it would be suitable?
