2011/9/29 Rico Schüller :
> 4. Implement each version on it's own, so each dll would get it's own code
> base. This way all differences could be handled correctly.
>
> Thus the only version which would really work 100% is #4, but due to not
> knowing the small differences and the huge amount of wor
Am 29.09.2011 00:13, schrieb Erich Hoover:
On Wed, Sep 28, 2011 at 2:45 PM, Alexandre Julliard wrote:
...
In general it's better to have the individual dlls handle their own
differences, instead of requiring d3dx9_36 to handle all the quirks of
20 different versions.
It sounded like we were on
On Wed, Sep 28, 2011 at 2:45 PM, Alexandre Julliard wrote:
> ...
> In general it's better to have the individual dlls handle their own
> differences, instead of requiring d3dx9_36 to handle all the quirks of
> 20 different versions.
It sounded like we were only talking about some functions not ex
On 09/28/2011 11:03 PM, Rico Schüller wrote:
> Am 28.09.2011 22:18, schrieb Erich Hoover:
>> 2011/9/28 Rico Schüller:
>>> ...
>>> d3dx9_25 and 24 needs it's own implementation because it's not only
>>> the last
>>> function which changed and that way it would look the same for all
>>> forwarding ef
Am 28.09.2011 22:18, schrieb Erich Hoover:
2011/9/28 Rico Schüller:
...
d3dx9_25 and 24 needs it's own implementation because it's not only the last
function which changed and that way it would look the same for all
forwarding effect interfaces in d3dx9_2{4,5,6}.dlls.
I'm not an expert on this
Erich Hoover writes:
> 2011/9/28 Rico Schüller :
>> ...
>> d3dx9_25 and 24 needs it's own implementation because it's not only the last
>> function which changed and that way it would look the same for all
>> forwarding effect interfaces in d3dx9_2{4,5,6}.dlls.
>
> I'm not an expert on this area,
2011/9/28 Rico Schüller :
> ...
> d3dx9_25 and 24 needs it's own implementation because it's not only the last
> function which changed and that way it would look the same for all
> forwarding effect interfaces in d3dx9_2{4,5,6}.dlls.
I'm not an expert on this area, but I'd be tempted to implement
Am 28.09.2011 16:43, schrieb Erich Hoover:
SetRawValue is at the end of the table, so it being extra will not
influence any older application. So, you should be able to get the
same functionality with way less code by adding that alternative GUID
to the QueryInterface in d3dx9_36.
Erich Hoover
SetRawValue is at the end of the table, so it being extra will not
influence any older application. So, you should be able to get the
same functionality with way less code by adding that alternative GUID
to the QueryInterface in d3dx9_36.
Erich Hoover
ehoo...@mines.edu