Forum Discussion
Import/Export Trigger in Storyline
Hi - I am trying to create a complex simulation which has the feature of giving feedback on all the learner has done on the screen. This involves many variables and loads of if...then...else in the triggers. While this is possible, it quickly becomes hard to keep track of all the trigger rules and conduct maintenance on them.
For this it would be very helpful, to be able to export all triggers from a slide (e.g. to csv or xls), edit them in an external tool (e.c. excel) and re-import them.
While it is clear that I have to be very careful to keep the integrity of all the 'names', this would be tremendously helpful.
Any way of accomplishing this?
Unfortunately not JMCruyff . I completely get where you are coming from as the if/else triggers can quickly become difficult to maintain.
One method I have used to make it a little easier to maintain is to use "layers" as functions. This can help you to organise the triggers to a certain degree.
For example, you might have a layer that sets the state of certain elements based on certain conditions. You can name the layer appropriately "func: Reset", and have that layer hide itself when the timeline ends. Therefore, to call a function/procedure, you just show a layer.
It's the best I've come up with.
I would love an advanced trigger window that allowed you to build/manage triggers through hand coding.
Thanks for the advice!
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!
