Buttons and toggles

TL;DR — Buttons fire once. Toggles stay on or off. Both drive Rive booleans you control live.

The difference

Buttons are one-shot triggers. Press them, something happens, they reset.

  • Play animation
  • Reveal a graphic
  • Flash a goal alert

Toggles are persistent switches. Press them, the state holds until you press again.

  • Show / hide the scoreboard
  • Mute / unmute an animation loop
  • "Is Live" indicator on or off

Behaviour comparison

| Control | State holds? | Auto-reset? | Use case | |---|---|---|---| | Button | No | Yes, back to false | Trigger effects, fire alerts | | Toggle | Yes | No, manual only | Show/hide elements, persistent flags |

Create one

Quadraviz reads booleans from your Rive file and surfaces them in the controller.

  1. In Rive, add a Boolean input to your state machine.
  2. Save and upload the .riv to Quadraviz.
  3. The boolean shows up in the live controller as a toggle.
  4. To make it a button instead, open the input settings in the controller and switch the mode.

You can flip any boolean between button and toggle behaviour from the controller without re-uploading.

Naming

Name the boolean in Rive the way you want it to appear in the controller. ShowScore is readable; bool_3 isn't.

Coming soon

Multi-state toggles (three or more options) are in development. For now, you can chain two booleans to express a three-state setup if needed.

Next steps

← Previous

Timers

Next

Set up the Live Controller