Chris1990
Junior Member level 1
Found this while trying to implement xbox controller...:
https://www.autohotkey.com/board/topi...-guide-button/
iv implemented two of the ordinals mentioned, the power off and i also have guide button detect implemented..
However, the other two ordinals are VERY useful considering my intended purpose of the guide button.
These are XInputWaitForGuideButton and XInputCancelGuideButtonWait..
However, i dont understand the UnKnown* punknown variable..
its called LPVOID here: **broken link removed**
and LPOVERLAPPED here:
https://code.google.com/p/x360ce/sou...c=svn514&r=514
However, both of these are c++, not c#, and i dont understand what variable they are meant to be in order to convert/implement/use them
Please help!!
Cheers
Chris
PS:
potential solution is to implement my own background thread and use that to essentially do what that does.. poll the button and return or wait until its pressed..
if a secondary background thread were to be implemented, the Cancel would have to neutralise the thread..
However, this wouldnt be strictly threadsafe from the point of view that the xbox controller might be accessed by two threads simultaneously.. hence why im trying to use these functions..
(just an after thought)
https://www.autohotkey.com/board/topi...-guide-button/
iv implemented two of the ordinals mentioned, the power off and i also have guide button detect implemented..
However, the other two ordinals are VERY useful considering my intended purpose of the guide button.
These are XInputWaitForGuideButton and XInputCancelGuideButtonWait..
However, i dont understand the UnKnown* punknown variable..
its called LPVOID here: **broken link removed**
and LPOVERLAPPED here:
https://code.google.com/p/x360ce/sou...c=svn514&r=514
However, both of these are c++, not c#, and i dont understand what variable they are meant to be in order to convert/implement/use them
Please help!!
Cheers
Chris
PS:
potential solution is to implement my own background thread and use that to essentially do what that does.. poll the button and return or wait until its pressed..
if a secondary background thread were to be implemented, the Cancel would have to neutralise the thread..
However, this wouldnt be strictly threadsafe from the point of view that the xbox controller might be accessed by two threads simultaneously.. hence why im trying to use these functions..
(just an after thought)