Forum Discussion
Storyline 360 and realising your triggers are a cluster ****
I was wondering what do other people do when they are working on a complex system with triggers that span multiple slides and then half way through you realise you've developed a trigger system that could be simplified by at least half the triggers you're already using. So with that in mind...
OPTION A: Do you push a-head and create a very detailed guide as reference to continue your mangled mess of triggers?
OPTION B: Do you change up half way through and use your much better trigger system and leave what is already done alone, hoping you'll never have to revisit the project again?
OPTION C: Do you modify every slide you've already worked on to make sure they follow the new system before you continue building the remaining slides?
I found myself in one of these problems recently and I'll be honest I adopted option B.
4 Replies
The statement by EricSchaffer-d1 that someone may have to edit the course is a great point. My project currently will not get edited, so if it works, forge ahead and circle back. If something unforeseen happens you will have more time.
I like what PhilMayor is saying in rebuilding. But I try to avoid this by thinking out my triggers before I lay pencil to paper. What I want to happen and when I want it to happen. But when I get to where you are I rebuild. Working for a Gobal company my story. file may go overseas to be adjusted to the region and revoiced to many different languages, may triggers need to match a best practica. If they are too confusing, I may get asked to rebuild anyway. So, I do a lot more preplanning, and I keep a lot of notes and storyboarding. Not that it doesn't change most of the time, but it helps.
I didn't say what EricSchaffer-d1 said purposefully. I started typing and deleted it. But I agree completely.
I test, test, test! Anything complex is always built as functioning blocks that each work before I move onto the next stage. Planning is important and I would never duplicate without getting functionality working right.
I would rebuild. To manage triggers I often build them almost as functions:
I put the triggers on a layer to fire on timeline start and add a hide trigger at the end.
I put the triggers on a hidden shape to fire on timeline start and add a trigger to hide the shape at the end.
Both times I call the layer or change state to normal to fire the triggers off.
IF it was to be on multiple slides I would have built the functions on the master and trigger them using variables.
