Separate input-handled-state for different events during physics-picking #79546
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.
Currently the input-handled-state for different events during physics-picking can interfere with each other, which means, that
is_input_handled
works only forControl
-nodes.This PR makes sure, that the input_handled_state is reset before processing an InputEvent during physics-picking, so that
is_input_handled
can additionally be used forNode2D
/Node3D
physics-picking.While #76439 is not fixed, this PR will not work, when physics-picking happens in a
SubViewportContainer
.resolve #79539