Allow implementations of IInputHandler to process handled events #222
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📝 Description of the Change
Previously, the
ProcessHandledEventsflag was defined on theInputProcessor, but this offered limited value: only the first handler could process the event, and if it marked it as handled, subsequent handlers were skipped regardless of their intent.By moving
ProcessHandledEventsto theIInputHandlerlevel, each handler can now independently decide whether it wants to receive already-handled events.🐛 Possible Drawbacks
This is a breaking change, as it modifies the location of the
ProcessHandledEventsproperty. However, I believe the impact is minimal, as this feature is unlikely to be widely used in its previous form.