at, Oct 25, 2008 at 4:54 PM, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:wine-devel-
>> [EMAIL PROTECTED] On Behalf Of Andrew Fenn
>> Sent: Saturday, October 25, 2008 6:43 PM
>> To: Juan Lang
>
2008/10/25 Stefan Dösinger <[EMAIL PROTECTED]>:
> The difference is (among others) that the first parameter is passed in the
> ECX register instead of the stack
>
No, that would be thiscall. The main difference between stdcall and
cdecl is who's responsible for popping arguments from the stack
(cal
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wine-devel-
> [EMAIL PROTECTED] On Behalf Of Andrew Fenn
> Sent: Saturday, October 25, 2008 6:43 PM
> To: Juan Lang
> Cc: wine-devel@winehq.org
> Subject: Re: DWORD help
>
> Thanks Juan. It's fixed n
> > I have written the following but when I have dwUserIndex as 0,1,2,3
> or
> > any number, doesn't really matter, it always returns
> > ERROR_BAD_ARGUMENTS.
>
> Not sure why it's not returning ERROR_DEVICE_NOT_CONNECTED for you.
> I'll just point out:
Probably the calling convention is wrong. Us
Thanks Juan. It's fixed now.
On Sat, Oct 25, 2008 at 5:13 PM, Juan Lang <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
>> I have written the following but when I have dwUserIndex as 0,1,2,3 or
>> any number, doesn't really matter, it always returns
>> ERROR_BAD_ARGUMENTS.
>
> Not sure why it's not retu
Hi Andrew,
> I have written the following but when I have dwUserIndex as 0,1,2,3 or
> any number, doesn't really matter, it always returns
> ERROR_BAD_ARGUMENTS.
Not sure why it's not returning ERROR_DEVICE_NOT_CONNECTED for you.
I'll just point out:
> DWORD XInputGetState(DWORD dwUserIndex, XIN
I have written the following but when I have dwUserIndex as 0,1,2,3 or
any number, doesn't really matter, it always returns
ERROR_BAD_ARGUMENTS.
DWORD XInputGetState(DWORD dwUserIndex, XINPUT_STATE* pState)
{
FIXME("Stub - Controller: %d \n", dwUserIndex);
if (dwUserIndex >= 0 && dwUserIn
