Organizing trigger list

I'm creating a "main menu" slide, where the link-buttons change based on events on the linked page.  Cool beans, that is all working fine; but...

...My trigger list is huge.

I though that the triggers would file under their respective buttons, but many of them are driven by the start of the timeline or variable value changes, so they just clutter at the top. I can't move them around too much because I've come to understand that the list order is important.  Many of the triggers have "or" and "and" conditionals, and I'm trying to get those to match.

Is there a way I can print off my trigger list so that I can just see them all at one time?  Is there some other way to organize them? Assign them colors or something?

Thanks,

Pierre

5 Replies
Douglas Spencer

For big triggers lists, I have found the following things to be helpful.

  1. It is possible to associate triggers with an object, even if the object isn't visible on the slide.  Just like with the main timeline, you can trigger on timeline start. This method is also good for copying and pasting triggers onto a different slide because all you need to do is copy and paste the object.
  2. You can also organize triggers in a layer but this gets tricky if they need to access the timeline or states of other objects. You would also need to load the layer from the base layer on timeline start.
Christie Pollick

Hi, Pierre -- Thanks for your question! As you mentioned, The Order in Which Triggers Are Executed in Articulate Storyline is very important! Unfortunately, as shared in this post on a similar topic, there is not a native function to print your trigger panel, but perhaps some of the alternative ideas shared might do the trick for what you have in mind. And don't forget to use this form to submit a feature request, as well!  :)

Christie Pollick

Thanks so much for passing along the Feature Request link to Lee, Wendy! And I wanted to note with respects to how Feature Requests are handled, ideas and suggestions are absolutely valued and are carefully considered by our Product Development team. You may find it useful to take a look at this oldie-but-goodie breakdown of our Feature Request Process by Product Operations Manager, Gabe Anderson. :)