<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><br><br>--- En date de : <b>Dim 1.2.09, Tony Wasserka <i><tony.wasserka@freenet.de></i></b> a écrit :<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">De: Tony Wasserka <tony.wasserka@freenet.de><br>Objet: Re: BOOL WINAPI versus BOOL in d3dx9 and d3dx8<br>À: wine-devel@winehq.org<br>Cc: jeremielapuree@yahoo.fr<br>Date: Dimanche 1 Février 2009, 14h45<br><br><pre>> Hi,<br>> <br>> the declaration of IntersectionTri is<br>> BOOL IntersectionTri(.....) in d3dx8mesh.h and BOOL WINAPI?<br>IntersectionTri(.....) in d3dx9mesh.h .<br>> <br>> Is the latter one compatible with the former one (so I can forward d3dx9<br>function to the d3dx8 one)<br>> or must I implement them separately?<br>> <br>> David<br><br>It's already forwarded in d3dx9_36.spec to d3dx8, so you don't
need to<br>implement it twice.<br>I was pretty careful when creating that specfile, i.e. it's in 99% safe to<br>trust it ;)<br><br>As a rule of thumb, every d3dx9 function which has no device (or any other D3D9<br>specific interface) parameter<br>and has the exact same parameter list can safely be forwarded to d3dx8.<br><br>However, are you sure it's only BOOL in d3dx8? AFAIK, dll functions always<br>have to be WINAPI,<br>as the calling convention gets screwed up otherwise...<br><br>Best regards, Tony<br><br>Yes, in the directx8 sdk the prototype is BOOL, not BOOL WINAPI.<br><br>David<br></pre></blockquote></td></tr></table><br>