Christian Costa <titan.co...@gmail.com> writes:
> 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 ?
Adding private extensions is not allowed, unless you can make a very
convincing argument that there's no other possible option.
--
Alexandre Julliard
julli...@winehq.org
