Grouping triggers

Jun 06, 2017

Hello,

I made gauges for a serious game. I had to create many triggers to display the right state of the gauge (built like a button with multiple states / and the gauge was stuck in the master slide). And I had so many triggers to built that, when I forgot one, the next one built comes at the top bottom of the list. And it was not easy to check that every trigger was there, especially since one can only move a trigger from one step at a time.

Daoes any one know if there is a way to rank and move faster triggers.

If not, I think gathering triggers could be a great improvement.

Thank you for your attention

13 Replies

Michael Anderson

almost 7 years ago06/06/17 at 7:10 pm (UTC)

I think this is a great suggestion, to be able to group triggers together for organization within the project.

Ashley Terwilliger-Pollard
Staff

almost 7 years ago06/07/17 at 8:56 pm (UTC)

Hi Benoit,

I could see how that would be really helpful to group and organize triggers! I get lost myself sometimes in a very long trigger panel. If you haven't already, can you submit a Feature requests here.

If you’re wondering what happens when you submit a feature request, here’s our process.

BENOIT GUILLO
Author

almost 7 years ago06/08/17 at 7:20 am (UTC)

Hello Ashley,

Ok, I submit a feature request today. Thank you. Have a good day.

Alyssa Gomez
Staff

almost 7 years ago06/09/17 at 6:29 pm (UTC)

Thanks for taking the time to submit the request, Benoit! It's much appreciated. 😊

Bryce Wescott

over 6 years ago08/20/17 at 6:31 pm (UTC)

As an avid Captivate user for years, I have always been perplexed by the lack of this feature in Storyline.

I primarily use SL2 (now 260) for courses that need JS because the interface and ease of use are beautiful. However, the trade off is that I often have courses that are muddled with 200+ triggers because of the duplicative nature of many objects.

I, personally, submitted a request for this years ago and am avidly waiting for this update! Captivates Advanced Actions and Shared Actions features are the key reason Captivate users do not switch. Implementing this feature in 360, there would be a great use case for many users to ditch Adobe for Storyline.

As it currently stands, without that feature, many will not switch (and those of us that use both painfully drudge through the mess of triggers).

BENOIT GUILLO
Author

almost 5 years ago05/07/19 at 7:45 am (UTC)

Hello Articulate staff,

Is there any response about this feature ? I could understand that such a feature is not a priority or is abandoned for x or y reason, that's Articulate choice. But could we have a response ?

Thank you for your work

Alyssa Gomez
Staff

almost 5 years ago05/07/19 at 9:30 pm (UTC)

Hello, Benoit!

Thanks for checking in. We've still got our eyes on this request as we consider new features for the upcoming updates in Storyline 360.

If we add changes to the trigger panel in the future, we'll let you know!

almost 5 years ago05/23/19 at 10:03 pm (UTC)

I'd like to know either way. (:

Alyssa Gomez
Staff

almost 5 years ago05/24/19 at 3:59 pm (UTC)

You're in the right place, Onoda! If we make changes to trigger panel functionality in the future, we'll let you know!

Khamla Vonsensey

almost 5 years ago06/11/19 at 1:51 pm (UTC)

I agree with everyone else, a grouping options for triggers would help a lot :)

almost 5 years ago06/12/19 at 1:16 pm (UTC)

Thanks, Khamla! We'll keep you posted here with any updates.

Al Lauer

almost 5 years ago06/14/19 at 1:09 pm (UTC)

Grouping triggers would be a huge plus. It'd also be nice to be able to add comments to trigger groups or individual triggers (as programmers would do in code) to alert others who are using your template what does what and where they would need to modify things for a different action/reaction. Thanks!

Kevin Reagh

over 3 years ago08/20/20 at 6:12 pm (UTC)

Not sure if this addresses what folks are looking for, but when I want to collect triggers into a group that can be executed from different buttons, I put the triggers on a layer (there is nothing else on that layer) and have the triggers fire when the layer's time line starts. The last trigger on the layer is "stop this layer's timeline". When I want the triggers to fire I show that layer. Hope that makes sense.