Fix incorrect ActionData::axis_pair
value when handling multiple DualAxisData
#457
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
The previous PR (#450) removed the accumulation for
ActionData::axis_pair
inInputMap::which_pressed()
, resulting in a problem where multipleDualAxisData
updates would only preserve the last one due to the loss of previously recordedDualAxisData
.A Simple Reproduction Case
While it functions correctly when pressing WASD, if only the arrow keys were pressed,
ActionState::axis_pair()
will returnNone
.Solution
Re-implement the accumulation of
ActionData::axis_pair
inInputMap::which_pressed()
.Changelog
ActionData::axis_pair
ButtonState::JustPressed
check by moving it into theinput_pressed
checking block and remove thepressed
flag