Question--if say I have a trigger on a button and copy and paste the trigger onto another button, and the original trigger has, say, eight conditions, on it, should the pasted trigger have the same eight conditions exactly as on the original?
If yes, then I might be seeing a bug and what to confirm before I report it.
I'm able to set up a few conditionals on a trigger and copy from one slide to another, however on the first trigger i have the user click an object on the slide. On the copied trigger that converts to a key press. I'm guessing that's because the same object wasn't on the next slide?
Thanks, Bill! I'd expect that. More a trigger to another slide and some of the references are broken.
I should have been clearer. I was talking about on the same slide, where you may have many buttons and layers and the learner is free to navigate through the slide as they like but you don't want them to move forward until they have seen everything. With that, you have to plan for any sort of clicking of buttons and multiple conditions that are the same on certain buttons.
What I'm seeing is the conditions change. You may have eight conditions on the trigger and eight conditions get pasted but it's not uncommon for one to change (like a "double" of another condition) with the paste, and, then, sometimes all come through just fine.
I reported a bug like this with regard to states during Beta testing, but haven't had a chance to see if it was fixed prior to release. On the bug I sent them, I had a number of states attached to a character (for example, smiling when clicked). I created two additional characters and then tried copying the properties from the original to the two new ones to see if all state attributes transferred. Some did and some didn't. Sounds like perhaps the issues wasn't completely addressed, and that it may be an issue at a deeper level if it applies to both triggers and states. Certainly the point of a copy feature is that all attributes should copy exactly; that's pretty much the definition of "copy" right there. . It's definitely something that needs exploring.
3 Replies
I'm able to set up a few conditionals on a trigger and copy from one slide to another, however on the first trigger i have the user click an object on the slide. On the copied trigger that converts to a key press. I'm guessing that's because the same object wasn't on the next slide?
Thanks, Bill! I'd expect that. More a trigger to another slide and some of the references are broken.
I should have been clearer. I was talking about on the same slide, where you may have many buttons and layers and the learner is free to navigate through the slide as they like but you don't want them to move forward until they have seen everything. With that, you have to plan for any sort of clicking of buttons and multiple conditions that are the same on certain buttons.
What I'm seeing is the conditions change. You may have eight conditions on the trigger and eight conditions get pasted but it's not uncommon for one to change (like a "double" of another condition) with the paste, and, then, sometimes all come through just fine.
Think I better file a bug . . .
I reported a bug like this with regard to states during Beta testing, but haven't had a chance to see if it was fixed prior to release. On the bug I sent them, I had a number of states attached to a character (for example, smiling when clicked). I created two additional characters and then tried copying the properties from the original to the two new ones to see if all state attributes transferred. Some did and some didn't. Sounds like perhaps the issues wasn't completely addressed, and that it may be an issue at a deeper level if it applies to both triggers and states. Certainly the point of a copy feature is that all attributes should copy exactly; that's pretty much the definition of "copy" right there.
. It's definitely something that needs exploring.
This discussion is closed. You can start a new discussion or contact Articulate Support.