I have a project that uses a number of buttons in the same layout (same location, labels) on just about every slide. I'd like to be able to add these to a slide master and apply them to various slides, but be able to modify the triggers for the buttons on each of the slides. I don't think that's possible.
If I need to change the original button layout (# of buttons, labels), I assume I would need to copy and paste the new configuration into many slides and reset the triggers. Is there a simple solution that I'm overlooking?
No there is no simpler way than you have mentioned.
Unfortunately, button triggers are not able to be changed in edit view when the button is on the master slide.
Be aware, when a button is on a master slide, the layers it may be controlling can also be on the master slide.
Also be aware, that those objects on the master slide will always be displayed behind objects in the edit view, therefore, if you have something slide in and out on the master slide (for example), it will display behind anything you have in the slide.
One way I've done this is by adding the button to the master slide and remoting to a listener on the slide itself. For example:
Create a variable called goNext
Adjust Variable goNext to add 1 When Next-button clicked
On your slide itself, create a shape and add triggers to the shape:
Jump to slide X when variable goNext changes.
This decouples the visual for the button from the logic. Lets you place the button and readjust in a single place and modify the action at the slide level.
it's been a long time - hope you are still available to help! Could you help me figure out how to make the back button on my master slide go to the last page visited vs. having to pick an individual slide? Your advice for the creating the variable and trigger for my "next slide" worked great on my master slide! Thanks in advance for your help!
Thank you Walt and Wendy for your advice yet that is not an option given. I am in the Slide Masters and when I click on my menu button for "back" and create a "jump to" trigger, it gives me my entire list of slides or "next slide" as options. There is no option "jump to previous slide".
Hi, Melissa -- Thanks for reaching out, and welcome to the community! I see that Wendy and Walt are assisting you here, but it may be most helpful if you were able to share your file or a screenshot of what you are seeing. To share, please use the grey ADD ATTACHMENT button in the bottom left of the reply box and you will be able to browse from there!
Thank you Wendy for helping! As for what I see when in the Masters Slide and clicked on my "back button", my "jump to" list is either "next slide" or individual slides (I included an attachment of my screen options - there are more slides listed below this as options). "Jump to previous" is not listed.
Sorry to be a pain yet I have scrolled through all the slides listed and there is no "previous slide" listed. I attached a screen grab earlier for reference. Thanks again!
I wish I could share my file for you to see "what the hell is going on here?" yet I signed a non-disclosure. Maybe I have time to start a new file with generic elements and see if I am getting the same response. Thanks again!
It has been a while since you posted this, but I came across it a few months ago when I was looking for tips on slide masters. I decided to use that approach. Which worked perfect!
However, recently I discovered serious navigation issues in the HTML output of my course. For some reason slides are skipped if I navigate forward, backwards, and then forward again. Also, hiding layers results in jumping to previous slides, etc... I logged an issue for this (#00910948).
I'm still not sure what causes the issue. In flash everything works as designed. The workaround is to go back to where I came from: adding all buttons and triggers to each slide manually.
I just thought, since you also use this approach, maybe you could share any thoughts or ideas on the subject?
Thanks for letting me know that you were also working in a case - I see that Cleo shared it's something that's been reported to our QA team so that we'll keep you posted on that behavior as well.
17 Replies
Hi Allan:
No there is no simpler way than you have mentioned.
Unfortunately, button triggers are not able to be changed in edit view when the button is on the master slide.
Be aware, when a button is on a master slide, the layers it may be controlling can also be on the master slide.
Also be aware, that those objects on the master slide will always be displayed behind objects in the edit view, therefore, if you have something slide in and out on the master slide (for example), it will display behind anything you have in the slide.
Best Regards,
Dennis Hall
One way I've done this is by adding the button to the master slide and remoting to a listener on the slide itself. For example:
On your slide itself, create a shape and add triggers to the shape:
This decouples the visual for the button from the logic. Lets you place the button and readjust in a single place and modify the action at the slide level.
Steve,
it's been a long time - hope you are still available to help! Could you help me figure out how to make the back button on my master slide go to the last page visited vs. having to pick an individual slide? Your advice for the creating the variable and trigger for my "next slide" worked great on my master slide! Thanks in advance for your help!
Jump to previous slide
Hi Melissa
just add a trigger to jump to previous slide
Thank you Walt and Wendy for your advice yet that is not an option given. I am in the Slide Masters and when I click on my menu button for "back" and create a "jump to" trigger, it gives me my entire list of slides or "next slide" as options. There is no option "jump to previous slide".
Thanks again for your help!
Hi Melissa
so at the top of your trigger list you don't see this?
Hi, Melissa -- Thanks for reaching out, and welcome to the community! I see that Wendy and Walt are assisting you here, but it may be most helpful if you were able to share your file or a screenshot of what you are seeing. To share, please use the grey ADD ATTACHMENT button in the bottom left of the reply box and you will be able to browse from there!
Thank you Wendy for helping! As for what I see when in the Masters Slide and clicked on my "back button", my "jump to" list is either "next slide" or individual slides (I included an attachment of my screen options - there are more slides listed below this as options). "Jump to previous" is not listed.
Scroll down, then back to the top.
Sorry to be a pain yet I have scrolled through all the slides listed and there is no "previous slide" listed. I attached a screen grab earlier for reference. Thanks again!
Hi Melissa!
Could you share your .story file for us to take a look?
Here's what I see in one of my files:
I wish I could share my file for you to see "what the hell is going on here?" yet I signed a non-disclosure. Maybe I have time to start a new file with generic elements and see if I am getting the same response. Thanks again!
Just let us know Melissa. Perhaps you could work with our team privately here. An NDA could be signed if needed.
Thank you so much for your help - I will check into that!
Hi Steve,
It has been a while since you posted this, but I came across it a few months ago when I was looking for tips on slide masters. I decided to use that approach. Which worked perfect!
However, recently I discovered serious navigation issues in the HTML output of my course. For some reason slides are skipped if I navigate forward, backwards, and then forward again. Also, hiding layers results in jumping to previous slides, etc... I logged an issue for this (#00910948).
I'm still not sure what causes the issue. In flash everything works as designed. The workaround is to go back to where I came from: adding all buttons and triggers to each slide manually.
I just thought, since you also use this approach, maybe you could share any thoughts or ideas on the subject?
Hi Lien,
Thanks for letting me know that you were also working in a case - I see that Cleo shared it's something that's been reported to our QA team so that we'll keep you posted on that behavior as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.