Fix consume status of mouse events in custom capture #967
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.
At present, it is not possible to consume events in the mouse event capture function, even if you return nil. This causes (among other things)
Application.draw()
to not fire properly, and essentially, means that any gui state changes you make inside the capture function, isn't rendered.This PR hopefully fixes that. I couldn't find any tests to modify/change, do you need any other info?
The following code (from the Application event loop) shows where the draw call would be skipped when the wrong consume status is returned