godot/tests
Markus Sauermann a9bf3de08e Fix InputEvent being used twice
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.
2023-05-29 02:39:09 +02:00
..
core Streamline WorkerThreadPool tests and make them more robust 2023-05-17 17:33:08 -04:00
data
python_build
scene Fix InputEvent being used twice 2023-05-29 02:39:09 +02:00
servers Add initial navigation tests 2023-02-13 21:39:09 +01:00
create_test.py One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00
display_server_mock.h Add Unit Tests for Viewport InputEvent handling 2023-02-09 14:53:04 +01:00
SCsub
test_macros.cpp One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00
test_macros.h Fix various errors when running the unit tests 2023-05-09 18:40:56 +02:00
test_main.cpp Streamline WorkerThreadPool tests and make them more robust 2023-05-17 17:33:08 -04:00
test_main.h One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00
test_tools.h One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00
test_utils.cpp One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00
test_utils.h One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00
test_validate_testing.h One Copyright Update to rule them all 2023-01-05 13:25:55 +01:00