Versions Compared

Version Old Version 3 New Version 4
Changes made by

Kyle (Unlicensed)

Kyle (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Identify the point in the interactive code (C++, C#, or Blueprints) where the user interaction for the data property begins. This could be a mouse capture, keypress, or other continuous input cycle.

  2. Within the update cycle, call the corresponding Begin Transient X Property Update, where 'X' refers to the datatype of the property.

    1. image-20250130-211853.png

  3. Identify the point in the interactive code (C++, C#, or Blueprints) where the user interaction for the data property begins. This could be a mouse capture, keypress, or other continuous input cycle.

  4. Within the update cycle, call the corresponding Begin Transient X Property Update, where 'X' refers to the datatype of the property.

    1. image-20250130-212321.png

    2. Identify the point in the interactive code (C++, C#, or Blueprints) where the user interaction for the data property begins. This could be a mouse capture, keypress, or other continuous input cycle.

    3. Within the update cycle, call the corresponding Begin Transient X Property Update, where 'X' refers to the datatype of the property.

...

Output

The image below displays the live output in the Journal for the connected Space. Notice the “T” icon on the left of each line representing the transient data update, followed by a corresponding finalized entry. When the user exits the Space, those Transient entries will be purged, and the finalized entries will remain as persistent Operations in the Journal history.

  • In some cases the Transient updates will be frequent, with only one finalized update.

  • Frequency of finalization is determined by the User Interface and the frequency of finalized calls.

...