Is there a utility or way to find triggers in my classes that are unassigned? Thankfully my beta testers typically find where I've failed to add triggers to move from one slide/layer to another, but I hate to leave that to chance. I tried to do a search on 'unassigned', but nothing came back (even when I purposely put one in the story for it to find).
If there isn't a utility to let you know your story is broken somewhere, it might be a nice addition. How do you find these nagging little errors?
I notice that triggers do not stay reliably intact when a scene is imported. It's time-consuming to have to touch each slide individually to validate functionality that was working 100% before import.
I second this comment! I have a lot of importing to do and it is such a pain resetting triggers, there is no reason they should be getting removed upon import. Articulate, please fix this!
29 Replies
9 years later... submitted it as another feature request.
This thread is 9 (!) years old and the problem is still not solved?
Stop making storyline to overloaded instead making it faster and easier to handle- thx!
Adding my name to this feature request...
I notice that triggers do not stay reliably intact when a scene is imported. It's time-consuming to have to touch each slide individually to validate functionality that was working 100% before import.
Thank you, support team!
I second this comment! I have a lot of importing to do and it is such a pain resetting triggers, there is no reason they should be getting removed upon import. Articulate, please fix this!