Enums

2m 30sPublished May 8, 2025

SummaryVersion Notes (Draft)

This lesson covers the concept and implementation of Enums (Enumerators) within Rive's framework. The primary educational objective is to show how utilizing "named values" instead of unnamed properties like numbers can significantly optimize State Machine logical controls. Using a playing card suit example, the video demonstrates how Enums enhance workflow clarity for developer integration and prevent runtime bugs by restricting input options to a predefined list.

Streamlining Runtime Collaboration: Utilizing Enums eliminates guesswork for engineering teams during runtime integration. Developers can write self-documenting code with clear semantic strings instead of mapping abstract integers like 0, 1, 2, or 3 to visual assets.
Data Validation & Constraints: Number inputs naturally accept out-of-bounds inputs which can potentially break animation states. Enums act as strict data validation gates, systematically blocking invalid data from ever entering the State Machine execution loop.
Two-Phase Workflow Architecture: Keep in mind that setting up Enums requires a distinct sequential workflow: you must first register the global list configuration template in the dedicated Enums panel before you can instantiate an operational property referencing it within your View Model.

📌 Key Points

Use enum values to represent discrete states and keep binding logic clearer.

📝 Notes

Markdown

0 chars

Step by Step

00:00:02

Concept Introduction:

Introducing Enums (Enumerators) as a method for creating named values. While driving card values with a number property is logical due to their inherent sequence, using numbers for abstract variations like card suits is non-intuitive, making Enums the ideal alternative.
00:00:52

Defining an Enum List:

Clearing out old number conditions from the suits State Machine layer, navigating to the Enums section in the hierarchy panel, and clicking the plus icon (+) to create enum 1. In the right-hand panel, add four custom options named hearts, clubs, diamonds, and spades.
00:01:18

Adding Property to View Model:

Switching to the View Model panel, hitting the plus (+) icon, and selecting the Enum option. In the property configuration dropdown, assign it to use the newly created custom template enum 1.
00:01:35

Setting the Default Initial State:

Highlighting the Enum property within the View Model list and utilizing the properties Inspector on the right to set the default initial active choice or theme (e.g., selecting hearts).
00:01:41

Mapping State Machine Conditions:

Selecting all the transition paths between the suit states inside the layer graph. Create a new condition for each transition using the newly established Enum property, and map them to equal their respective named options (hearts, clubs, diamonds, and spades) to complete the named logic.
00:02:12

Logical Benefits Wrap-up:

Demonstrating the final runtime control behavior. Explaining how controlling named values instead of numbers makes the implementation self-documenting for engineers and systematically caps the options to stop invalid data entry.