Hi. I have a trigger on a base slide that I can't seem to delete. I couldn't figure out why it was not working so I thought I'd delete it and re-create it, but when I click on the trigger the delete option is grayed out. I can edit it, or copy it, but cannot delete.
Hi. I realized that I was trying to attach the entire course, which is big. So I extracted the problem slide and it is attached.
So there are 2 issues:
1. On the base slide, there is a trigger that cannot be deleted -- it is the one where there is unassigned next to it. This really is not affecting the slide performance, but it is a puzzle as to why it cannot be deleted.
2. I have the slide set up to show Untitled Layer 2 when the user clicks NEXT and certain conditions are met; or to show Untitled Layer 3 when the user clicks NEXT and certain other conditions are met. No matter what, only Untitled Layer 3 shows up. This issue is the more critical.
I took a look at your .story file and you're right...it is puzzling. I can't seem to delete that trigger either. Odd. If it doesn't interfere with anything then just ignore it. If it bothers you, the only thing I can think of is recreate the slide as it appears to have gotten "stuck."
As for the behaviors of always showing Untitled Layer 3 no matter what the conditions may have something to do with tying those triggers to the Player Next button. That button is typically used for navigation "away" from or to another slide, and not showing/hiding layers within a slide.
I'd suggest creating a new button on the slide and attach those conditional triggers to it. And then turn off the Next/Prev buttons on the player all together. You already have the "continue" button on Untitled Layer 2 which I presume will navigate to the next slide in sequence.
Safe rule: Player navigation buttons for slide-to-slide. Layer navigation use new buttons.
Sorry to jump in - I was looking at the file as well. At first, I wasn't able to delete the trigger. However, after changing the trigger to another object (other than the "NEXT" button), I was able to remove it. I'm wondering if this may be due to the other triggers assigned to the "Next" button, but I'm not entirely sure. Was the slide copied at some point?
If you're still unable to delete it, though, Kevin's suggestion of recreating the slide may be a good idea!
I looked back to see what I did and it looks like I recreated the slide but also took away the NEXT button and added a new button to the slide to enable the learner to move to the next slide. And it worked. Granted, it means this slide has a slightly different look that the others but it doesn't seem to matter in this case.
If your problem is on one slide only perhaps that will work?
Glad that this thread was able to assist you as well Scott :) Thanks for popping in to share. It may not help the ones listed here since it's a bit dated, but it could certainly help others in the future.
Kind of late to the game, but I discovered a workaround for this problem -
I inserted a random shape to my slide and assigned the "un-deletable" trigger to refer to the new shape as its object. Then I simply delete the shape and the trigger is deleted along with it!
It's certainly never too late to share a solution as it could certainly assist those that run across this thread in the future. Thanks for popping in to share.
I ran into this same issue. Instead of recreating the slide, simply select all of the items on your slide, then cut and paste back on the same slide. This will remove all of those undeletable triggers!
I had a similar problem with the player button Next. Primarly, the Next button was disabled until the timeline ended. Then, I deleted the triggers for it, but the operation remained unaffected. I could only solve it by adding a new trigger, that changed the state of the Next button to normal, when the timeline starts.
I had the same problem. I fixed it by editing the undeletable trigger to be the same as one of the triggers I do want to use and then I deleted the duplicate (original) trigger keeping only the undeletable trigger.
I was running into this same problem and used Barbara Martins solution of creating an extra object to assign the trigger to then deleting the object (in this case a rectangle). Worked like a charm!
27 Replies
Can you please post the .story file so that we can have a look?
Many thanks
Bruce
Thank you so much for your offer to help. However, I seem to be having trouble attaching the file. Hmmm.
Hi. I realized that I was trying to attach the entire course, which is big. So I extracted the problem slide and it is attached.
So there are 2 issues:
1. On the base slide, there is a trigger that cannot be deleted -- it is the one where there is unassigned next to it. This really is not affecting the slide performance, but it is a puzzle as to why it cannot be deleted.
2. I have the slide set up to show Untitled Layer 2 when the user clicks NEXT and certain conditions are met; or to show Untitled Layer 3 when the user clicks NEXT and certain other conditions are met. No matter what, only Untitled Layer 3 shows up. This issue is the more critical.
Any help is greatly appreciated!
Adena
Hi Adena,
I took a look at your .story file and you're right...it is puzzling. I can't seem to delete that trigger either. Odd. If it doesn't interfere with anything then just ignore it. If it bothers you, the only thing I can think of is recreate the slide as it appears to have gotten "stuck."
As for the behaviors of always showing Untitled Layer 3 no matter what the conditions may have something to do with tying those triggers to the Player Next button. That button is typically used for navigation "away" from or to another slide, and not showing/hiding layers within a slide.
I'd suggest creating a new button on the slide and attach those conditional triggers to it. And then turn off the Next/Prev buttons on the player all together. You already have the "continue" button on Untitled Layer 2 which I presume will navigate to the next slide in sequence.
Safe rule: Player navigation buttons for slide-to-slide. Layer navigation use new buttons.
Hope this helps.
Sorry to jump in - I was looking at the file as well. At first, I wasn't able to delete the trigger. However, after changing the trigger to another object (other than the "NEXT" button), I was able to remove it. I'm wondering if this may be due to the other triggers assigned to the "Next" button, but I'm not entirely sure. Was the slide copied at some point?
If you're still unable to delete it, though, Kevin's suggestion of recreating the slide may be a good idea!
I hope you all have a great weekend,
Christine
Dear Kevin and Christine,
Thank you both!! Kevin, definitely appreciate the rule about player vs. layer navigation.
Christine, I'll try changing the trigger to another object -- but I may just end up recreating.
Again, thank you both for helping me out! Love this support community.
- Adena
I'm having the same issue. I added navigation controls after creating the project, using same process I've used successfully a few times before:
http://www.articulate.com/support/kb_article.php?product=st1&id=3nq6s9jfveap
My "next" button isn't working and, like Adena, I can't delete the triggers either.
Hi Chris,
I looked back to see what I did and it looks like I recreated the slide but also took away the NEXT button and added a new button to the slide to enable the learner to move to the next slide. And it worked. Granted, it means this slide has a slightly different look that the others but it doesn't seem to matter in this case.
If your problem is on one slide only perhaps that will work?
Sorry I can't be of more help.
Adena
Hi Chris and welcome to E-Learning Heroes! Let us know how Adena's solution works for you and if you need anything further.
Thanks Adena for popping back in with an update and helping Chris out
I had an image that I triggered to a scene and could not remove the trigger.
Based on this information, it deleted the image and copied a non=triggered version from another slide. I had to resize it,but it worked out for me.
Glad that this thread was able to assist you as well Scott :) Thanks for popping in to share. It may not help the ones listed here since it's a bit dated, but it could certainly help others in the future.
Kind of late to the game, but I discovered a workaround for this problem -
I inserted a random shape to my slide and assigned the "un-deletable" trigger to refer to the new shape as its object. Then I simply delete the shape and the trigger is deleted along with it!
Welcome to E-Learning Heroes Barbara :)
It's certainly never too late to share a solution as it could certainly assist those that run across this thread in the future. Thanks for popping in to share.
I ran into this same issue. Instead of recreating the slide, simply select all of the items on your slide, then cut and paste back on the same slide. This will remove all of those undeletable triggers!
That's a pretty cool idea Jeremy - thanks for popping in to share.
Welcome to E-Learning Heroes as well.
It worked!! Thank you!!!
Glad that this thread was able to help you out as well Kaylee :) Thanks for chiming in to share.
I had a similar problem with the player button Next. Primarly, the Next button was disabled until the timeline ended. Then, I deleted the triggers for it, but the operation remained unaffected. I could only solve it by adding a new trigger, that changed the state of the Next button to normal, when the timeline starts.
Hi Donata and welcome to E-Learning Heroes :)
That certainly sounds frustrating. Thanks for popping in to share how you were able to overcome this obstacle.
Are you able to recreate this in a new file? If so, I'd love to take a look.
This worked for me. Thanks!
Glad this older thread was able to help you out as well Michele.
Thanks for chiming in to share :)
Hi everyone. I know its been a while since people have posted here but the problem persists. Any word yet on the reason for this?
Greetings, Emma!
I replied in this discussion, so stopping by to connect the dots for anyone following along. 😊
I had the same problem. I fixed it by editing the undeletable trigger to be the same as one of the triggers I do want to use and then I deleted the duplicate (original) trigger keeping only the undeletable trigger.
I was running into this same problem and used Barbara Martins solution of creating an extra object to assign the trigger to then deleting the object (in this case a rectangle). Worked like a charm!