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
Input cleanup 2 #9689
Input cleanup 2 #9689
Conversation
def1c35
to
c91f802
Compare
Source/Core/InputCommon/ControllerEmu/ControlGroup/IMUGyroscope.h
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine otherwise, as far as I can tell anyway.
Source/Core/InputCommon/ControllerEmu/ControlGroup/Attachments.cpp
Outdated
Show resolved
Hide resolved
|
Oh, actually, two typos in commit messages that should probably be fixed!
|
af30044
to
32fad99
Compare
done everything |
7fc483e
to
5004a2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look fine. Could you rebase this on master to fix the Windows build failures?
only control[0] was checked, and not one, which seems random. Either both or none should be checked.
Similar to the guitar, only control[0] was checked, and that felt random.
casting a value to a u32 when it's originally an int, and it's exposed as int to users, could end up in cases where a negative number would result as a positive one. This doesn't really affect the value range of the attachment enum, still I think the code was wrong. Heavily tested.
…t, clean code My future PRs will split the UI state from the Emulation State of some of these emulated controller values and this readies the code for it.
Skimming of: #9489
A few fixes/improvements/cleanup for input related stuff, nicely described in commits.
Separated from #9688 because this one actually has behavioural changes and needs to be reviewed.