From 2d824e166a33081e4c224b368ddf7d0da39cf429 Mon Sep 17 00:00:00 2001 From: benoitalain <35855598+benoitalain@users.noreply.github.com> Date: Thu, 19 Dec 2024 12:13:44 -0500 Subject: [PATCH] DOCS: Improves DOCF-5483. (#2095) --- Packages/com.unity.inputsystem/Documentation~/UISupport.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Packages/com.unity.inputsystem/Documentation~/UISupport.md b/Packages/com.unity.inputsystem/Documentation~/UISupport.md index 8e196f820d..a904095279 100644 --- a/Packages/com.unity.inputsystem/Documentation~/UISupport.md +++ b/Packages/com.unity.inputsystem/Documentation~/UISupport.md @@ -32,6 +32,7 @@ The three main UI solutions are **UI Toolkit**, **Unity UI**, and **IMGUI**. The - From Unity 2023.2 and onwards, the UI actions defined in the default [project-wide actions](./ProjectWideActions.md) directly map to UI Toolkit input. You do not need to use the UI Input Module component.

- In versions of Unity prior to 2023.2, you must use the UI Input Module component to define which actions are passed through from the Input System to the UI. +- Refer to UI Toolkit [Runtime UI event system and input handling](https://docs.unity3d.com/Manual/UIE-Runtime-Event-System.html) for more information on how to configure UI Toolkit input. **For [**Unity UI**](https://docs.unity3d.com/Packages/com.unity.ugui@latest), also known as "uGUI" (a GameObject and Component style UI solution):**