Versions Compared

Version Old Version 3 New Version Current
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 cycleFind the event graph where the UI element is initial captured for editing. Then, call the corresponding Begin Transient X Property Update, where 'X' refers to the datatype of the property.

    image-20250130-211853.pngImage Removed

  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.

    image-20250130-212321.pngImage Removed

  4. 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.

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

...

    1. In the example below, a “Begin Transient FLOAT Property Update” is bound to the Mouse Capture for the UI element.

    2. The relative location of the slider component on blueprint asset is passed into the function to be stored as a TRANSIENT property.

    3. The output from the “Begin Transient X Property Update” function produces a Live X Updater object, which is used as a reference to continuously update the Journal while the UI is captured.

      image-20250130-222833.pngImage Added

  2. A “value change” event triggers a call to update the Journal with new data. The Live Value Updater variable created in the previous step provides a reference to connect the data update with the corresponding Transient entry in the Journal.

    1. image-20250130-212321.pngImage Added

  3. Add a “Finalize” blueprint function call to the end of the even graph where the UI element is released.

    1. This deletes the reference created in the “Live Value Updater” variable, and adds a persistent entry in the Journal with the latest value.

    2. In the example below, the relative location of the slider is stored in the Journal to be synchronized with other users in the Space.

...

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.

...