-
Notifications
You must be signed in to change notification settings - Fork 40
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
Separate menu input from per-player input #798
base: master
Are you sure you want to change the base?
Conversation
e8edd7b
to
90bc319
Compare
|
||
// Return success | ||
return 0; | ||
} | ||
|
||
int vector_swapdelete_at(vector *vec, unsigned index) { |
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.
The name feels a bit, but I couldn't come up with anything better. I considered making this the default, but I think we rely on vector keeping the order in most places. Blah.
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.
Probably better than it was. Might be a good idea to get an okay from @Vagabond too.
017e6d8
to
36d2939
Compare
The only things that are still controlled by per-player input (controller_poll) are Melee, Vs, and Arena.
Everything else now uses
game_state_menu_poll
, a drop-in replacement forcontroller_poll
that lets all detected input devices control the menus.Users are unable to rebind the keyboard menu controls, to avoid complications around textinput, multiple keys performing the same action, and ensuring no single key performs multiple actions.
All detected game controllers/joysticks generate menu input events, even when no player has a joystick bound.
Closes #499
Closes #266
Closes #265