a9bf3de08e
A single mouse click can cause multiple actions, which contradicts the paradigm that a single Input Event should cause only a single action. The solution consists of two parts: 1. Physics Picking as the last step during viewport input event handling, currently doesn't set the event as handled. This PR sets the event as handled in the case of physics picking. 2. After an InputEvent is processed by a SubVieportContainer, it is sent to its parent, even if it set as handled within the SubViewport. This PR adds an additional test to check if the event is handled before propagating the event to the parent Control. |
||
---|---|---|
.. | ||
test_animation.h | ||
test_arraymesh.h | ||
test_audio_stream_wav.h | ||
test_bit_map.h | ||
test_code_edit.h | ||
test_curve.h | ||
test_curve_2d.h | ||
test_curve_3d.h | ||
test_gradient.h | ||
test_navigation_agent_2d.h | ||
test_navigation_agent_3d.h | ||
test_node.h | ||
test_path_2d.h | ||
test_path_3d.h | ||
test_path_follow_2d.h | ||
test_path_follow_3d.h | ||
test_primitives.h | ||
test_sprite_frames.h | ||
test_text_edit.h | ||
test_theme.h | ||
test_viewport.h | ||
test_visual_shader.h |