Forum Discussion
Import/Export Trigger in Storyline
Like SamHill, I've also put triggers on invisible layers to make them easier to manage. That's especially handy when different actions on the base (such a clicking multiple buttons) need to perform the same series of triggers (such as a set of calculations).
Instead of every action (e.g., button clicks) needing to repeat every trigger in the series, just give those actions one trigger that shows the layer, and let the triggers run from there. Then close the layer when its set-as-short-as-possible timeline ends.
The other trick I use: giving objects, layers, and variables meaningful names that will keep similar items together. For example, I start button names with "b[#]," which keeps them in order in the Trigger Panel, since they're sorted alphanumerically. (I also name layers starting with "L[#]," so it's easy to troubleshoot, e.g., b1-intro shows L1-intro.)
Great point JudyNollet , the difference in maintaining a project, that using a consistent naming convention makes, cannot be overstated.
I've helped with so many Storyline files, and inherited Storyline files that just use the default names and it takes so much longer to work out what each element is doing. It's one of the first things I do when looking into a project, start naming elements according to what they do.
Thanks for the additional advice!
