Am I crazy? Why can't I copy a trigger from one slide to another without everything set to unassigned? I feel like I used to be able to do it but maybe not? It happens if I try to duplicate the object as well.
I am working with a local file in storyline version 3.52.25247.0. Here is a screencast of what I do and what happens; here is what I have tried
Creating a new copy of the file with a new name
Selecting the button on the next slide and not selecting it
Pasting the same trigger in the same slide works fine
Actually, you never have been able to copy triggers without them becoming unassigned. Actually, I think there was a time in early SL 2 when they looked like the original in the trigger pane, but didn't work. Then if you edited them, you found they were all set to unassigned.
It's because none of the objects they are attached to exist in the new slide. Even if you give them the same name, their secret, known-only to SL, internal name is different.
The only action that can be expected to work is duplicating a slide, or importing it from another SL
While I was sort of expecting that as the response, I am sad because it means I have a lot of triggers to update today. I wish duplicating the slide or importing was an option but unfortunately my project is near complete with the exception of this ONE next button trigger update at this point.
I will chalk it up as a lesson learned and I sure wont forget for future projects! I appreciate the help/confirmation Walt!
Actually...it depends. I've gathered if you make a clone of a course and then work on the new copy, expanding it and copy/pasting code around, it tends to work, even between the two projects. What I'm experiencing lately is instead far worse, as I sometimes copy a trigger and simply cannot paste it anywhere, the "paste" option in the trigger menu is greyed out. This is quite frustrating I must say.
I'm sorry you've hit this snag! I've done some testing with copying and pasting triggers in different parts of Storyline (e.g. Slide view, Story View, Slide Masters) and didn't get the same results.
Would be able to share any details about when you are experiencing this?
Is it happening in one specific project? If not, how often is it happening?
- I don't know yet if it's on a specific project as I only had to perform the action on the one project, not others. I guess I would have to experiment further to provide you with an informed answer. - I was using the 3.73.29904.0 version but I have now upgraded to the last one.
So far I haven't had a change to try and reproduce the bug. I'll keep you posted if that happens.
On a lighter note, I've managed to make the copy/paste work by closing and reopening the projects. I've also caught a glimpse of what I think may be the problem. As I pasted the scripts often I would soon (split/second time) move to another task, leaving the focus off of the current slide master. I speculate that is when the bug occurrs...can't be certain, though.
I am unable to replicate this behavior on my end, but the test files that I am using may not be as complex as your actual project files.
If you're already working locally, we recommend doing a repair of your Storyline 360 installation to see if this will help address the behavior. Doing the repair will also help make sure that you are working using a healthy installation.
6 Replies
Actually, you never have been able to copy triggers without them becoming unassigned. Actually, I think there was a time in early SL 2 when they looked like the original in the trigger pane, but didn't work. Then if you edited them, you found they were all set to unassigned.
It's because none of the objects they are attached to exist in the new slide. Even if you give them the same name, their secret, known-only to SL, internal name is different.
The only action that can be expected to work is duplicating a slide, or importing it from another SL
Thank you for confirming I am crazy Walt; hahaha!
While I was sort of expecting that as the response, I am sad because it means I have a lot of triggers to update today. I wish duplicating the slide or importing was an option but unfortunately my project is near complete with the exception of this ONE next button trigger update at this point.
I will chalk it up as a lesson learned and I sure wont forget for future projects! I appreciate the help/confirmation Walt!
Actually...it depends. I've gathered if you make a clone of a course and then work on the new copy, expanding it and copy/pasting code around, it tends to work, even between the two projects.
What I'm experiencing lately is instead far worse, as I sometimes copy a trigger and simply cannot paste it anywhere, the "paste" option in the trigger menu is greyed out.
This is quite frustrating I must say.
Hi Walter,
I'm sorry you've hit this snag! I've done some testing with copying and pasting triggers in different parts of Storyline (e.g. Slide view, Story View, Slide Masters) and didn't get the same results.
Would be able to share any details about when you are experiencing this?
Thanks for reaching out!
- I don't know yet if it's on a specific project as I only had to perform the action on the one project, not others. I guess I would have to experiment further to provide you with an informed answer.
- I was using the 3.73.29904.0 version but I have now upgraded to the last one.
So far I haven't had a change to try and reproduce the bug. I'll keep you posted if that happens.
On a lighter note, I've managed to make the copy/paste work by closing and reopening the projects.
I've also caught a glimpse of what I think may be the problem. As I pasted the scripts often I would soon (split/second time) move to another task, leaving the focus off of the current slide master. I speculate that is when the bug occurrs...can't be certain, though.
Hi Walter,
Thanks for the additional information.
I am unable to replicate this behavior on my end, but the test files that I am using may not be as complex as your actual project files.
If you're already working locally, we recommend doing a repair of your Storyline 360 installation to see if this will help address the behavior. Doing the repair will also help make sure that you are working using a healthy installation.
If the issue persists, open a case with our support team here so we can take a closer look at what's happening.