Forum Discussion
Programming the Slide Master
It would be helpful to be able to add triggers, actions, and layers to the Slide Master, but then customize the actual sequence of actions on the slide itself.
For Example -- I would like to be able to create layers within the Slide Master, but the have a trigger on each individual slide using that layout to show the applicable layer at a designated cue point on the individual slide, instead of having having only the base layer on the Slide Master and having to build each layer on each individual slide. I can create the base layer layout within the Master, but will have to program each individual slide's layers, cue points, and triggers. If we could build the Slide Master, with the layers, triggers, and cue points, etc. then all we would have to do is customize the slide (i.e., adjust the cue point, so the associated layer or action could be synched with the audio track.)
1 Reply
Giving this post a bump, I've started building a master/layout for our team and it isn't easy. Like what Jeff is running into, it is a lot of triggers, actions, and animations (also layers but I'm not using them as much in the master) not working properly despite them being options in the master editor.
I feel like the biggest problem is that most of the tools that are available in the master editor are carried over from the main editor despite them either not working or able to reference/edit when you move back from the master to main editor, like triggers, layers, cue points, animations, the timeline. Why include the options if they don't work properly, or at least give an article for how to use it because the current articles provide little to no help with these issues. This means that basically no logic/triggers/cues/animations/motion paths/accessibility tags get carried over 1to1 from the master/layout to the project slide, save for the placeholders. Even the HTML identifiers for the placeholders are indistinguishable from any other text box in the project, so there is no way to add in any JS code on the master to identify them for something like an animation or trigger when they are applied to a slide.
At this point I'm hesitant to even use the Slide Master tools because they barely do what they are supposed to do, and instead I'm probably going to need to resort to a "scene" that my team can import that includes my "master/layouts" and have them manually make copies for their projects. At least that way I can use all of the tools available and know that they will work the way they are intended.
