From e6990c1339bd9baad877107068efb7cc0ccbd373 Mon Sep 17 00:00:00 2001 From: Emily Date: Mon, 11 Dec 2023 17:09:46 -0800 Subject: [PATCH] Removed the part about areas not having the input event function called by default, it's not true --- tutorials/inputs/inputevent.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/tutorials/inputs/inputevent.rst b/tutorials/inputs/inputevent.rst index a341dcc7c..04639af5d 100644 --- a/tutorials/inputs/inputevent.rst +++ b/tutorials/inputs/inputevent.rst @@ -113,8 +113,7 @@ received input, in order: In the case of a 3D scene if a :ref:`Camera3D ` is assigned to the Viewport, a ray to the physics world (in the ray direction from the click) will be cast. If this ray hits an object, it will call the :ref:`CollisionObject3D._input_event() ` - function in the relevant physics object (bodies receive this callback by default, but areas do - not. This can be configured through :ref:`Area3D ` properties). + function in the relevant physics object. In the case of a 2D scene, conceptually the same happens with :ref:`CollisionObject2D._input_event() `. When sending events to its child and descendant nodes, the viewport will do so, as depicted in