Widget Services

////////////////////////////////////////

Purpose

////////////////////////////////////////

Monobehaviours to load scenes and intantiate prefabs. The template objects can be either prefabricated game objects or addressable memory content.

Create lists of Audio Clips and Textures to pass to the Widget Services.

Code methods to create behaviours on game objects to inter communicate between user interface components like the text or button ui behaviours.

The methods to send messages can be added at runtime or edit time.

The goal is to allow for runtime UI creation and automated testing.

⦁Workflow for Sending Data: Efficiently send data between addressable scenes and addressable prefabs.

⦁Data Connection Implementation: Connect user interface components input and output sockets for transfering objects. Save and load data for each widget.

⦁Scene and Screen Handlers: Load and unload addressable scenes and prefabs seamlessly. Handles screen orientations and scaling.

⦁Testing and Automation Interface: Test and automate using data connections by sending messages to widgets.

Works in Edit Mode and Run Time.

Each UI behavior includes a component called a Widget, such as Button Widget. The Button Widget handles the heavy lifting by implementing inputs and outputs that connect to UI behavior methods. You can set the text label or receive the button click with the label as the data. Messages are sent with object GUIDs, decoded by the destination object for a method, and parsed for results that are set in the UI behavior.