Unity Debug Sheet

[日本語ドキュメント(Japanese Documents Available)](https://github.com/Haruma-K/UnityDebugSheet/blob/master/README_JA.md) Hierarchical debug menu system for Unity that makes it easy to create intuitive and organized debug menus.

Eyecatch

## Table of Contents

Details

- [Overview](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#overview) - [Concept and Features](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#concept-and-features) - [Demo](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#demo) - [Setup](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#setup) - [Requirements](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#requirements) - [Installation](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#installation) - [Quick Start](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#quick-start) - [Place the prefab in the scene](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#place-the-prefab-in-the-scene) - [Create the debug page](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#create-the-debug-page) - [Add a link to the debug page.](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#add-a-link-to-the-debug-page) - [Open and close the debug menu](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#open-and-close-the-debug-menu) - [Result](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#result) - [Basic Usage](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#basic-usage) - [List of Available Cells](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#list-of-available-cells) - [List of Available Pages](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#list-of-available-pages) - [Update the cell contents](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#update-the-cell-contents) - [Workflow in multiple scenes](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#workflow-in-multiple-scenes) - [Exclude from the release builds](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#exclude-from-the-release-builds) - [Custom Cells](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#custom-cells) - [Advanced Usage](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#advanced-usage) - [Use async methods instead of coroutines](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#use-async-methods-instead-of-coroutines) - [Hide Backdrop](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#hide-backdrop) - [Don't close the debug menu when the backdrop is clicked](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#dont-close-the-debug-menu-when-the-backdrop-is-clicked) - [Change the Show/Hide animations](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#change-the-showhide-animations) - [Work within the safe area](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#work-within-the-safe-area) - [Change the min/max size of the debug menu](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#change-the-minmax-size-of-the-debug-menu) - [Customize the look](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#customize-the-look) - [Pop multiple screens at once](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#pop-multiple-screens-at-once) - [Extending Built-in Cell Prefabs](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#extending-built-in-cell-prefabs) - [Extension Packages](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#extension-packages) - [Display the system information of Unity](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#display-the-system-information-of-unity) - [In-game Debug Console](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#in-game-debug-console) - [Graphy](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#graphy) - [Licenses](https://github.com/Haruma-K/UnityDebugSheet/raw/master/#licenses)

## Overview ### Concept and Features In general, many debug commands are created during game development, and the number of them increases as development progresses. As a result, it becomes difficult to find the desired command, which in turn leads to a decrease in development efficiency. **Unity Debug Sheet** allows you to easily create a debug menu with a hierarchical structure. Its GUI can be easily and intuitively controlled by anyone, especially on mobile platforms.

Debug Sheet

Of course, it also supports vertical layout.

Vertical Layout

Adding debug commands is also easy. ```cs // Label AddLabel("Example Label"); //　Button AddButton("Example Button", clicked: () => { Debug.Log("Clicked"); }); // Switch AddSwitch(false, "Example Switch", valueChanged: x => Debug.Log($"Changed: {x}")); // Slider AddSlider(0.5f, 0.0f, 1.0f, "Example Slider", valueChanged: x => Debug.Log($"Value Changed: {x}")); ``` ### Demo You can try the demo by cloning `this repository itself and playing the demo scenes. The following demo scenes are av`ailable. **Character Viewer: CharacterViewerDemo.unity** This demo allows you to switch between character models, motions, etc. from the debug menu. It also include samples that integrate with other libraries such as [Graphy](https://github.com/Tayx94/graphy) and [In-Game Debug Console](https://github.com/yasirkula/UnityIngameDebugConsole) to monitor performance.

Character Viewer Demo

**Default Cells: DefaultCellsDemo.unity** This demo allows you to check the behavior of all the cells (generic name for items such as button, labels, and sliders, etc.) that are included in this library by default.

Default Cells Demo

**Custom Cells: CustomCellsDemo.unity** In addition to the default cells, you can create your own custom cells. This demo shows how to create custom cells.

Custom Cells Demo

**Entry Scene: DemoEntry.unity** The above three scenes can also be transitioned from the this scene. You can see how the debug sheet placed in each scene behaves as singleton. ## Setup ### Requirements This tool is compatible with the following environments. - Unity 2020.3 or later ### Installation You can install this library by the steps below. 1. Select **Window > Package Manager** from the menu bar. 2. Click the **+** button in the upper left corner of the window and select **Add package from git URL...**. 3. Enter the following URL in the input field and click **Add**. ``` https://github.com/Haruma-K/UnityDebugSheet.git?path=/Assets/UnityDebugSheet ```

Package Manager

Or, you can also install by adding the following line to the `dependencies` block of `manifest.json` file in the `Packages` folder. ```json { "dependencies": { "com.harumak.unitydebugsheet": "https://github.com/Haruma-K/UnityDebugSheet.git?path=/Assets/UnityDebugSheet" } } ``` If you want to specify the version, you can do so by adding the version number to the end of the URL. ``` https://github.com/Haruma-K/UnityDebugSheet.git?path=/Assets/UnityDebugSheet#1.0.0 ``` You can update the version by changing the version number above. If you do not specify the version, you can update it by opening the file `Packages/package-lock.json` and rewriting the hash of this library. ```json { "dependencies": { "com.harumak.unitydebugsheet": { "version": "https://github.com/Haruma-K/UnityDebugSheet.git?path=/Assets/UnityDebugSheet", "depth": 0, "source": "git", "dependencies": {}, "hash": "..." } } } ``` ## Quick Start This section shows an easy way to set up and use the Unity Debug Sheet. ### Place the prefab in the scene First, drag and drop the prefab named **DebugSheetCanvas** to **Hierarchy** window to place it in the scene. And if **EventSystem** not exists, create it.

Debug Sheet Canvas

### Create the debug page Next, create a page for debugging. Create the page by inheriting from `DefaultDebugPageBase` as shown below. The following is an example page with a single button that logs **Clicked** when clicked. ```cs using System.Collections; using UnityDebugSheet.Runtime.Core.Scripts; using UnityEngine; public sealed class ExampleDebugPage : DefaultDebugPageBase { protected override string Title { get; } = "Example Debug Page"; public override IEnumerator Initialize() { // Add a button to this page. AddButton("Example Button", clicked: () => { Debug.Log("Clicked"); }); yield break; } } ``` ### Add a link to the debug page. Next, add a link to transition to the debug page created above. Get the root page and add a link button to it as shown below. ```cs using UnityDebugSheet.Runtime.Core.Scripts; using UnityEngine; public sealed class DebugSheetController : MonoBehaviour { private void Start() { // Get or create the root page. var rootPage = DebugSheet.Instance.GetOrCreateInitialPage(); // Add a link transition to the ExampleDebugPage. rootPage.AddPageLinkButton(nameof(ExampleDebugPage)); } } ``` > **NOTE** > If you want to use your own page as the root page instead of linking as above, use `Initialize()` instead of `GetOrCreateInitialPage().AddPageLinkButton Open/Close the debug menu

This behavior can be changed from the **Flick To Open** on the **Debug Sheet** component. You can enable only the left or right side of the screen, or disable flick operation.

Flick To Open

> **Warning** > In the Unity editor, this range is not necessarily 6mm because it simulate the resolution of the actual device. > It is recommended to also use the operation with keyboard shortcuts described below. You can also open and close the debug menu by pressing the button. To do this, set the click area from **Click To Open** on the **Debug Sheet** component. You can set the number of times you need to click in a row to open it in **Click Count To Open**.

Click To Open

You can use keyboard shortcuts to open and close the debug menu. In default, **Control (Command on Mac) + Shift + D** toggles the debug menu. Shortcuts can be freely changed from **Keyboard Shortcut** on the **Debug Sheet** component.

Keyboard Shortcut

And you can also open/close the debug menu from your script as below. ```cs // These scripts are attached on the GameObject "DebugSheetCanvas > Drawer". StatefulDrawer drawer; StatefulDrawerController drawerController; // Toggle debug sheet. var isClosed = Mathf.Approximately(drawer.Progress, drawer.MinProgress); var targetState = isClosed ? DrawerState.Max : DrawerState.Min; drawerController.SetStateWithAnimation(targetState); ``` ### Result With the implementation up to this point, you can confirm that the debug menu works as follows.

Result

## Basic Usage This section describes the basic usage of the Unity Debug Sheet. The Quick Start section is the prerequisite, so please read it first. ### List of Available Cells In default, you can use the following cells. | Cell Name | Method Name to Add | Description | | --- | --- | --- | | Label | AddLabel | Used to display strings. | | Button | AddButton | Used to trigger actions when clicked. | | InputField | AddInputField | Used to input text. | | Switch | AddSwitch | Used to switch ON and OFF. | | Slider | AddSlider | Used to specify a numerical value within a range. | | Picker | AddPicker | Used to select one of several options. | | Enum Picker | AddEnumPicker | Used to select one of the elements of the enum. | | Multi Picker | AddMultiPicker | Used to select more than one from multiple options. | | Enum Multi Picker | AddEnumMultiPicker | Used to select more than one from the elements of the enum. | | Search Field | AddSearchField | Used to display the search field. | | Page Link Button | AddPageLinkButton | Used to transition to the other debug pages when clicked. | | Button Collection | AddButtonCollection | Use when you want to display many small buttons. | You can check the behavior of each cell by playing the [Default Cells Demo Scene](https://github.com/Haruma-K/UnityDebugSheet/raw/master/Assets/Demo/02_DefaultCells/Scenes/DefaultCellsDemo.unity). You can also create your own cells. See the Custom Cells section for more information about this. ### List of Available Pages You can use the following pages in default. | Class Name | Description | | --- | --- | | DebugPage | Page with methods for adding default cells. | | FloatingButtonPage | Page with a floating button at the bottom. If you need to a button, such as a "Submit" button, you can use this page. | | DefaultDebugPageBase | Base class for the debug page that has methods for adding default cells. It is an abstract class, so you need to inherit it to use. | | DebugPageBase | Base class for the debug page. It is an abstract class, so you need to inherit it to use. | ### Update the cell contents Using **CellModel**, you can update the contents of the cell that has been generated. The following is an example of renaming a generated button each time the **Space** key is pressed. Please refer to the comments for details. ```cs using System.Collections; using UnityDebugSheet.Runtime.Core.Scripts; using UnityDebugSheet.Runtime.Core.Scripts.DefaultImpl.Cells; using UnityEngine; public sealed class ExampleDebugPage : DefaultDebugPageBase { private int _buttonCellIndex; private ButtonCellModel _buttonCellModel; private int _counter; protected override string Title => "Example Debug Page"; public override IEnumerator Initialize() { // Create the CellModel and set data and events. var buttonCellModel = new ButtonCellModel(false); buttonCellModel.CellTexts.Text = GetButtonName(); buttonCellModel.Clicked += () => { Debug.Log("Clicked"); }; // Keep the index of the cell and the CellModel. _buttonCellIndex = AddButton(buttonCellModel); _buttonCellModel = buttonCellModel; yield break; } private void Update() { if (Input.GetKeyDown(KeyCode.Space)) { // Update the cell data _counter++; _buttonCellModel.CellTexts.Text = GetButtonName(); // Refresh the target cell. RefreshDataAt(_buttonCellIndex); // You can also refresh all data by calling RefreshData(). //RefreshData(); } } private string GetButtonName() { return $"Example Button {_counter}"; } } ``` ### Workflow in multiple scenes In default, **DebugSheetCanvas** is used as a singleton. That is, if **DebugSheetCanvas** is placed in two scenes, the one instantiated first will be used and the one loaded later will be destroyed. In this case, initialization should be only be done on the first `DebugSheet`. If the order of scene loading is not guaranteed, you can use `DebugSheet.GetOrCreateInitializePage()` to get a page that has already been initialized, if any, and initialize it. Please refer to the **DemoEntry** scene for the workflow in multiple scenes. Note that if you do not want to use it as singleton, you can do it by unchecking **Singleton** in the **DebugSheet** component.

Singleton

### Exclude from the release builds You should exclude **GameObject**, script files, and resources files related to the debug menu from the release builds. You can exclude all scripts of the **Unity Debug Sheet** by adding **EXCLUDE_UNITY_DEBUG_SHEET** to the **Scripting Define Symbols** in the **Player Settings**. Thus, if you enclose all your own code that accesses the **Unity Debug Sheet** with `#if EXCLUDE_UNITY_DEBUG_SHEET`, you can exclude all the code from the release builds. It may also be a good idea to combine your own scripts that accesses the **Unity Debug Sheet** into a single assembly and set **Define Constraints** in the **asmdef**. In addition, you can completely exclude the debug menu from your build by doing the following. - Delete the **Resources** folder containing the debug menu resources if you have created. - Delete the **GameObject** containing the **DebugSheet** component in your scenes. ### Custom Cells To create your own cell, first create a component that inherits from **Cell** and a model that inherits from **CellModel** to set data to it. ```cs using UnityDebugSheet.Runtime.Core.Scripts; using UnityEngine; using UnityEngine.UI; public sealed class CustomTextCell : Cell { [SerializeField] private Text _text; [SerializeField] private LayoutElement _layoutElement; private const int Padding = 36; protected override void SetModel(CustomTextCellModel model) { _text.text = model.Text; _text.color = model.Color; _layoutElement.preferredHeight = _text.preferredHeight + Padding; } } public sealed class CustomTextCellModel : CellModel { public string Text { get; set; } public Color Color { get; set; } = Color.black; } ``` Then, create a GUI, attach this component to it, and make it a prefab. Due to the implementation of the cell recycling system, the following points should be taken into account when implementing the cell. - Attach a **Layout Element** to the root **GameObject** and input a height in the **Preferred Height** property. - Set the width of the cell to a fixed value. Next, set this cell to **Cell Prefabs** on the **Debug Sheet**.

Cell Prefabs

All that remains is to add this cell to the page. Please refer to [the demo scene of the custom cells](https://github.com/Haruma-K/UnityDebugSheet/raw/master/Assets/Demo/03_CustomCells/Scenes/CustomCellsDemo.unity) for the actual implementation. ## Advanced Usage ### Use async methods instead of coroutines You can also use asynchronous methods instead of coroutines to define lifecycle events of debug page, as shown below. ```cs using UnityDebugSheet.Runtime.Core.Scripts; using System.Threading.Tasks; public class SomePage : DefaultDebugPageBase { protected override string Title => "Some Page"; // Using asynchronous methods to define lifecycle events public override async Task Initialize() { await Task.Delay(100); } } ``` To use asynchronous methods, add `Scripting Define Symbols` in the following steps. * Player Settings > Other Settings * Add `UDS_USE_ASYNC_METHODS` to `Scripting Define Symbols`. Note that `Scripting Define Symbols` needs to be set for all platforms. ### Hide Backdrop In default, the black GUI is displayed as the backdrop of the debug menu. You can hide it if you want by deactivating the **GameObject** of **DebugSheetCanvas > Backdrop**.

Disable Backdrop

### Don't close the debug menu when the backdrop is clicked In default, the debug menu is closed when the backdrop is clicked. You can disable this behavior by unchecking **Close When Backdrop Clicked** in the **Stateful Drawer Backdrop Controller** component attached to the **DebugSheetCanvas > Drawer**.

Close When Backdrop Clicked

### Change the Show/Hide animations You can change the Show/Hide animations by changing the **AnimationDuration** and **AnimationCurve** properties in the **Stateful Drawer** component attached to the **DebugSheetCanvas > Drawer**.

Animation Settings

### Work within the safe area By default, the debug menu appears from outside the screen, and is placed outside the screen when it is hidden. You can work it within the safe area by checking **Move Inside Safe Area** property in the **Debug Sheet Drawer** component attached to the **DebugSheetCanvas > Drawer**.

Move Inside Safe Area

### Change the min/max size of the debug menu You can also change the min/max size of the debug menu. If you changed this, it can always be displayed at the bottom of the screen, even when minimized, as shown below, for example.

Set Min/Max Size

To change the size of each state, edit the properties of the **Debug Sheet Drawer** attached to **Debug Sheet Canvas > Drawer**. Adjust the **Min's Progress** to change the size shen minimized and *Size* to change the size when maximized. **Middle** is the middle size applied when held vertically.

Set Min/Max Size

You can apply and check the size of each state by clicking **Set State** button in **Debug** area.

Size Debugging

### Customize the look Unity Debug Sheet consists of uGUI, so you can freely customize the look by adjusting the properties. - Color of the back and close buttons - Color of the backdrop - Text color of the title The design of each cell can be freely customized by creating a custom cell. See the Custom Cells section for more information on this. ### Pop multiple screens at once You can pop multiple pages at once. To do this, specify the number of pages to be popped in the second argument of `DebugSheet.PopPage()`. ```cs DebugSheet debugSheet; debugSheet.PopPage(true, 2); ``` You can also specify the destination `PageID`. `PageID` can be obtained using the `onLoad` callback of `PushPage()` as shown below. ```cs DebugSheet debugSheet; debugSheet.PushPage(true, onLoad: x => { var pageId = x.pageId; }); ``` In addition, you can specify any ID by specifying the `pageId` argument of `PushPage()`. ```cs DebugSheet debugSheet; debugSheet.PushPage(true, pageId: "MyPageId"); ``` In addition, for the pages that are skipped when popping multiple pages, the lifecycle events before and after transition will not be called, only the event before destroying will be called. And the transition animation of the skipping pages will not be played. ### Extending Built-in Cell Prefabs You can extend built-in cell prefabs such as LabelCell and ButtonCell by following the steps below: 1. Create a Prefab Variant of the built-in Prefab and make any desired modifications. 2. Ensure the name of this Prefab is the same as the original Prefab. 3. Set this Prefab in the **Cell Prefabs** of the **Debug Sheet** component. ## Extension Packages ### Display the system information of Unity Yuo can display the system information of Unity easily by this package.

System Info

Following features are now available. | Class name of DebugPage | Description | | --- | --- | | SystemInfoDebugPage | Show the information of SystemInfo class. | | ApplicationDebugPage | Show the information of Application class. | | TimeDebugPage | Show the information of Time class. | | QualitySettingsDebugPage | Show the information of QualitySettings class. | | ScreenDebugPage | Show the information of Screen class. | | InputDebugPage | Show the information of Input class. | | GraphicsDebugPage | Show the information of Graphics class. | | PhysicsDebugPage | Show the information of Physics class. | | Physics2DDebugPage | Show the information of Physics2D class. | Usage is as follows. 1. (Only if you use your own assembly) Add [UnityDebugSheet.Unity](https://github.com/Haruma-K/UnityDebugSheet/raw/master/Assets/UnityDebugSheet/Runtime/Extensions/Unity/UnityDebugSheet.Unity.asmdef) to the referenced assemblies. 2. Write as `DefaultDebugPageBase.AddPageLinkButton("System Info")` to add page link cell. ### In-game Debug Console This is an extension package that links the **Unity Debug Sheet** with [**In-game Debug Console**](https://github.com/yasirkula/UnityIngameDebugConsole) that is the OSS for displaying the console at runtime. By this package, you can easily add a debug menu to display the console.

In-game Debug Console

Usage is as follows. 1. Install & Setup [**In-game Debug Console**](https://github.com/yasirkula/UnityIngameDebugConsole). (There are several ways to install.) 2. (Only if you install 1. not via Package Manager) Add `UDS_INGAMEDEBUGCOSOLE_SUPPORT` to Scripting Define Symbols and restart Unity. 3. (Only if you use your own assembly) Add [UnityDebugSheet.IngameDebugConsole](https://github.com/Haruma-K/UnityDebugSheet/raw/master/Assets/UnityDebugSheet/Runtime/Extensions/IngameDebugConsole/UnityDebugSheet.IngameDebugConsole.asmdef) to the referenced assemblies. 4. Write as `DefaultDebugPageBase.AddPageLinkButton("In-Game Debug Console", onLoad: x => x.page.Setup(DebugLogManager.Instance));` to add page link cell. ### Graphy This is an extension package that links the **Unity Debug Sheet** with [**Graphy**](https://github.com/Tayx94/graphy) that is the OSS to display FPS, Memory, etc...

Graphy

Usage is as follows. 1. Install & Setup [**Graphy**](https://github.com/Tayx94/graphy). (There are several ways to install.) 2. (Only if you install 1. not via Package Manager) Add `UDS_GRAPHY_SUPPORT` to Scripting Define Symbols and restart Unity. 3. (Only if you use your own assembly) Add [UnityDebugSheet.Graphy](https://github.com/Haruma-K/UnityDebugSheet/raw/master/Assets/UnityDebugSheet/Runtime/Extensions/Graphy/UnityDebugSheet.Graphy.asmdef) to the referenced assemblies. 4. Write as `DefaultDebugPageBase.AddPageLinkButton("Graphy", onLoad: x => x.page.Setup(GraphyManager.Instance));` to add page link cell. ## Licenses This software is released under the MIT License. You are free to use it within the scope of the license, but the following copyright and license notices must be displayed when using it. - [LICENSE.md](https://github.com/Haruma-K/UnityDebugSheet/blob/master/LICENSE.md) In addition, the table of contents of this document was created using the following software - [toc-generator](https://github.com/technote-space/toc-generator) The following software is used in the demo scenes. - [https://github.com/yasirkula/UnityIngameDebugConsole](https://github.com/yasirkula/UnityIngameDebugConsole) - [https://github.com/Tayx94/graphy](https://github.com/Tayx94/graphy) See Third Party Notices.md for details on these licenses.