This repository was archived by the owner on Sep 7, 2021. It is now read-only.
In response to issue #36 #38
Open
GameOverture wants to merge 1 commit intojkuhlmann:contribfrom
GameOverture:contrib
Open
In response to issue #36 #38GameOverture wants to merge 1 commit intojkuhlmann:contribfrom GameOverture:contrib
GameOverture wants to merge 1 commit intojkuhlmann:contribfrom
GameOverture:contrib
Conversation
…eived both a 'down' and 'up' message in the same update. This array then apply itself to InputDevice's previousState_ so these inputs can be detected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Added an array to
InputDevicethat keeps track of any button that received both a 'down' and 'up' message in the same update. This array then apply itself toInputDevice'spreviousState_so these inputs can be detected.Note that I assume these input devices are manipulated using messages from the platform, specifically the Windows platform. I'm not familiar with how other platforms work in this library, but this should only affect code that uses the
HandleButton(...)function (besides the additional memory footprint of oneArray<>in eachInputDevice