Forum Discussion

SPMS02's avatar
SPMS02
Community Member
1 month ago

Suggestions on triggers

  1. Grey out deactivated triggers without crossing them out. This makes deactivated triggers easier to read.
  2. Some triggers (like the one highlighted below) can only be moved downward but not upward. Is this a bug?
  3. Do not automatically reorder amended/newly created triggers. There were instances when my amended/newly added triggers were shifted to a new location even though it is within the same object. Finding the shifted triggers can be very tedious when there are many similar triggers.
  4. Currently dial variable increases when the dial is rotated clockwise. In math and physics simulations, we need dial variables to increase when the dial is rotated anti-clockwise. Can this be done?
  5. Allow triggers to be grouped and accessed like subroutines in programming languages.
  6. Remove the 0 from a numeric input field. This occurs during runtime when the user replace the default NumericEntry variable with his own variable. 
  7. Enhance math operations. At the moment, adding two variables together requires two triggers. 

My email is Tan_Teow_Chye@ichat.sp.edu.sg

Thank you.

1 Reply

  • EricSantos's avatar
    EricSantos
    Staff
    1 month ago

    Hello SPMS02,

    Thanks for taking the time to share these suggestions! It’s clear you’re working with more advanced trigger setups, and I can see how these enhancements would improve both efficiency and usability.

    I’ve shared your ideas with our product team, including improving the readability of disabled triggers, giving authors more control over trigger ordering, allowing customizable dial direction, enabling grouping of triggers for better organization, adding flexibility to numeric input defaults, and simplifying math operations within triggers.

    Regarding trigger movement, the behavior you’re seeing where some triggers can only be moved in one direction is typically due to how Storyline manages execution order. Triggers run from top to bottom, and in some cases, Storyline limits how they can be reordered to prevent logic conflicts. That said, I understand how this can feel restrictive when working with more complex setups, and I’ve included that as part of the feedback.

    For the dial behavior, there isn’t currently a way to reverse the direction. As a workaround, you can invert how the variable is used, for example, by subtracting it from the maximum value, so it behaves like it increases when rotated anti-clockwise.

    Thanks again for such thoughtful and detailed input.