On Wed, 20 Apr 2005, Alexandre Julliard wrote:
Francois Gouget <[EMAIL PROTECTED]> writes:
I had a look in this area in the past but it's really complex so I
don't think I'll tackle it. I'll just tweak Wine and winapi_check to
reduce the size of the winapi_check output so it's less overwhelming.
Wh
Francois Gouget <[EMAIL PROTECTED]> writes:
> I had a look in this area in the past but it's really complex so I
> don't think I'll tackle it. I'll just tweak Wine and winapi_check to
> reduce the size of the winapi_check output so it's less overwhelming.
While you are cleaning things, it would b
On Wed, 20 Apr 2005, Vincent Béron wrote:
[...]
If anyone has an idea for a better fix (or if you know of other APIs
that should have the same problem) I'm all ears as I don't like this
solution much.
If you're heading that way (a bit of spring cleaning of winapi_check),
could you also look at how
On Wed, 20 Apr 2005, Christian Costa wrote:
Hi Francois,
I plan to flatten the ddraw directory and perform some file renaming.
This will fix the problem once done.
Great. Then it's best not to apply my patch. This way we won't have to
remove it later.
--
Francois Gouget [EMAIL PROTECTED]
Hi Francois,
I plan to flatten the ddraw directory and perform some file renaming.
This will fix the problem once done.
Bye,
Christian
> Message du 20/04/05 11:39
> De : "Francois Gouget"
> A : [EMAIL PROTECTED]
> Copie à :
> Objet : Ugly dclipper winapi_check
Le mer 20/04/2005 à 05:29, Francois Gouget a écrit :
>
> winapi_check assumes that all the functions declared in a given spec
> file are implemented in a C file located in the same directory. This
> seems to hold true except for DirectDrawCreateClipper() which is
> implemented in a sub-director
