Francois Gouget <[EMAIL PROTECTED]> writes:
> From their header file actually. It contains the following comment:
>
> * Thus for the api MCIWndCreate, there are in fact two apis,
> * MCIWndCreateA and MCIWndCreateW. If you call MCIWndCreate, this will be
> * re-routed to MCIWndCreateA unless UNICODE is defined when building your
> * application. In any one application, you can mix calls to the
> * Ansi and Unicode entrypoints.
>
> Also they indicate this API was already there in the Win3.1 times.
> Everything else is just an educated guess.
MCIWndCreate is simply an alias for MCIWndCreateA, presumably for
compatibility with apps compiled before #ifdef UNICODE was
invented. So we should make both point to MCIWndCreateA in the spec
file, there's no need for a separate definition or a prototype.
--
Alexandre Julliard
[EMAIL PROTECTED]