godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-05 22:09:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

Renames / fixes for Godot 4

Browse Source
This commit is contained in:
Max Hilbrunner
2022-10-16 20:36:12 +02:00
parent e12fcc3da4
commit 99d3d0be12
25 changed files with 72 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
tutorials/inputs/input_examples.rst
View File

@@ -210,7 +210,7 @@ the :kbd:`T`:
}
}
.. tip:: See :ref:`@GlobalScope_KeyList <enum_@GlobalScope_KeyList>` for a list of keycode
.. tip:: See :ref:`@GlobalScope_Key <enum_@GlobalScope_Key>` for a list of keycode
constants.
.. warning::
@@ -261,7 +261,7 @@ different when it's :kbd:`Shift + T`:
}
}
.. tip:: See :ref:`@GlobalScope_KeyList <enum_@GlobalScope_KeyList>` for a list of keycode
.. tip:: See :ref:`@GlobalScope_Key <enum_@GlobalScope_Key>` for a list of keycode
constants.
Mouse events
@@ -275,7 +275,7 @@ means that all mouse events will contain a ``position`` property.
Mouse buttons
~~~~~~~~~~~~~
Capturing mouse buttons is very similar to handling key events. :ref:`@GlobalScope_ButtonList <enum_@GlobalScope_ButtonList>`
Capturing mouse buttons is very similar to handling key events. :ref:`@GlobalScope_MouseButton <enum_@GlobalScope_MouseButton>`
contains a list of ``BUTTON_*`` constants for each possible button, which will
be reported in the event's ``button_index`` property. Note that the scrollwheel
also counts as a button - two buttons, to be precise, with both

4
tutorials/inputs/inputevent.rst
View File

@@ -91,8 +91,8 @@ received input, in order:
event will not spread any more. The unhandled input callback is ideal for full-screen gameplay events, so they are not received when a GUI is active.
4. If no one wanted the event so far, and a :ref:`Camera3D <class_Camera3D>` is assigned
to the Viewport with :ref:`Object Picking <class_viewport_property_physics_object_picking>` turned on, a ray to the physics world (in the ray direction from
the click) will be cast. (For the root viewport, this can also be enabled in :ref:`Project Settings <class_ProjectSettings_property_physics/common/enable_object_picking>`) If this ray hits an object, it will call the
:ref:`CollisionObject._input_event() <class_CollisionObject_method__input_event>` function in the relevant
the click) will be cast. (For the root viewport, this can also be enabled in :ref:`Project Settings <class_ProjectSettings_property_physics/common/enable_object_picking>`.) If this ray hits an object, it will call the
:ref:`CollisionObject._input_event() <class_CollisionObject3D_method__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 <class_Area3D>` properties).
5. Finally, if the event was unhandled, it will be passed to the next