SOFlow v1.3

- Added the Simple Game Event Listener component. This is a stripped down version of the Game Event Listener, with only the minimum set of features required for an event listener.

- The header for all inspectors now contain a special SOFlow subheader. This subheader currently only contains a shortcut button to add a Simple Game Event Listener to the currently selected game object, but will be expanded upon in future iterations of the SDK.

- This release introduces Dynamic Inspector Fields. These are like little add-ons on top of simple data types like strings and ints. Important Note: They only support inspectors that are drawn through the SOFlow SDK. It is not required to add any form of support for these add-ons. No field attributes!

Current Dynamic Inspector Fields are :
1. The Dynamic Numeric Slider. This add-on allows us to turn any simple numerical field into a slider equivalent. The min and max ranges for the slider are also adjustable.

2. The Dynamic Text Area. This one allows us to turn any string field into a text area. The size of the text area is adjustable.

3. The Object History Picker. This one is a bit special and only works when objects are selected through the normal Unity object picker window (image below). Whenever an object is selected through the Unity object picker, SOFlow keeps track of what objects have been selected. The Object History Picker now allows us to assign object references from this history list to object fields that support the Object History Picker add-on. Essentially, this add-on is a "most recently used" list for object references.

Below demonstrates each Dynamic Inspector Field in use.

This is the script used in the above demonstration. As we can see, no special attributes, imports or inheritance were needed for the Dynamic Inspector Fields to work.

- Primitive Data can now be directly dragged into their associated fields. This saves the added step of first needing to swap to a reference field before being able to drag a Primitive Data reference into the field.

- Scriptable Objects can now be selected from a dropdown list. The Scriptable Object class simply needs to inherit from DropdownScriptableObject available from this release of the SDK and onwards.

- The [AssignComponent] attribute has made its way to the SDK this release. [AssignComponent] works exactly like the built-in [RequireComponent] attribute by Unity, but can be applied to variables directly. What makes [AssignComponent] unique is its ability to automatically assign the component it requires to the variable it is attributed to. This saves on some boilerplate code, as well as potential missing reference errors that can occur when using [RequireComponent]. [AssignComponent] also has two parameters.

The first parameter is a type that can be specified. When a type is specified, [AssignComponent] attempts to find that specific type on the game object, and if not found, will create it on the game object and assign the newly created component to the variable. When this parameter is not specified, [AssignComponent] will default to the type of the variable it is attributed to.

The second parameter is a bool flag to say whether [AssignComponent] should try to find components inside child game objects as well. This parameter is false by default.

- Inline Data Field Events have been added to all primitive data fields. These events will be called whenever the value of the field has changed. Along with this, all Data Fields and Primitive Data have had their event signatures updated. They now return the exact type of their value to the event callbacks.