Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GetStateEx support #23

Merged
merged 1 commit into from
Dec 16, 2023
Merged

GetStateEx support #23

merged 1 commit into from
Dec 16, 2023

Conversation

Originalimoc
Copy link
Contributor

Not Option<>, I believe this will never get removed

@Lokathor
Copy link
Owner

The code seems good. I'm not sure what you mean by "Not Option<>" though

@Originalimoc
Copy link
Contributor Author

Originalimoc commented Nov 30, 2023

Existing code treat some external functions Option<T>, this one is not, meaning if loading Ordinal 100 failed the program return Err, code is tested

@Lokathor
Copy link
Owner

If it's an Ex function that didn't exist in some early version of XInput, then it needs to be optionally loaded.

Using option or not is about compatibility back to old XInput versions, not a concern that the functions will go away in a future version.

@MaulingMonkey
Copy link
Contributor

GetStateEx wasn't introduced until XInput 1.3. It's also an undocumented function exported by ordinal only.
Steam, Origin, etc. use it however - so it's probably fairly safe to rely on.

@Lokathor Lokathor merged commit 2956814 into Lokathor:master Dec 16, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants