# Minimal UI Minimal UI is a new set of modern drawers for bind fields built on UI Toolkit. It is simpler, more compact and customizable than the legacy UI (here named Verbose UI). The thinking behind Minimal UI is to try to have as much bind field control and information as possible in a single line of Unity Inspector. Going forward, this UI will become the standard one. It also has some exclusive additional features, such as Group rebinding and more.

The Minimal UI is optional, and can be enabled in Binding Settings. Here are some of its features: * Drag and drop objects to change source and/or path:\ No need to expand the Source Field to change the source, just drag the object over the path field and the path popup will show up automatically, or if the new object is compatible with current path, it will only replace it.

* Collapse or expand additional fields:\ Converters and Source Field are not essential all the time, they can be collapsed. The expand information is serialized and will persist with the bind field.

* Quick shortcuts, hold Ctrl (or Cmd on MacOS) and click:\ For BindMode, it will trigger on and off the LiveDebug.\ For Source Field, it will ping the object.

* Compact Modifiers:\ Some modifiers have only one field, and it space consuming to have the foldout only for one field. The field may be rendered directly instead of foldout. Add `[OneLineModifier]` attribute over class definition to let it render as in the examples below.

* Improved Tooltips:\ The tooltips have been greatly improved to contain dynamic data, such as whe LiveDebug is active and the errors present in the fields. The use of different colors further enhance some aspects for tooltips.

* Bind fields in groups. Groups are formed either by headers or by foldouts, such as complex types or arrays.\ Currently there are 2 ways of rebinding groups of bind fields:\ \- SMART: will replace only bind fields which have paths compatible with dragged object.\ \- FORCED: will replace all bind fields regardless of path compatibility.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://postica.gitbook.io/binding-system/product/minimal-ui.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.