I was looking for some insight. I am creating my own player basically adding a bar on the bottom of each slide with custom buttons such a Replay and a Map icon, to show progression. I have found by doing this I will have to copy and paste the bar on every slide, since we are using full screen View Mode screen recordings, I can not put the bar on a master slide.
Has anyone does this before, that might have some helpful tips?
I haven't tried that recently so I may be wrong but, have you tried inserting your bar on a layer on the master slide? In most cases, that would appear on top of the base layer of a regular slide.
I place navigation stuff on the master slide in a layer. A couple of sticky wickets you'll have to contend with.
The first is the wackiness of some triggers and events on the master slide. You can't target certain things from a master slide for some reason. Luckily, there is a trick that works every time. I create a numeric variable and make the button on the layer increment this value by one when clicked. Then I create a variable listener trigger on the base of the master slide (or on the slide itself if I want to vary the behavior). When I click the button, the event bubbles up to the listener and executes what I want.
The second problem is your nav layer could be hidden or written on top of by slide objects and layers. For this, I use the variable increment trick again. When variable showNav changes, show layer navigation. This gets the navigation layer to leap to the front. I change the variable at the start of the master slide. I also add a trigger to the feedback master for my default layer style. This ensures that when a new layer is shown, it will show the master navigation layer even if the layer is set to hide other layers. Jumps the nav layer right to the front.
I've done the same thing using a layer on the master slide pop up with some custom navigation options. There was one problem though that I couldn't get around. I had 5 buttons, Menu, Prev Scene, Prev Slide, Next Slide, Next Scene. The Menu, Prev Scene and Prev Slide worked, but not the Next Slide and Next Scene. I've tried different methods to try to make them work (even the increment trick) and they never went to the next slide or next scene.
My advice, is to some extensive testing before you go all out. Even though you really only have to make changes to one slide/layer, make sure it works before you get to a point where your entire course will rely on it.
One of the problems in SL1 was the next slide trigger will jump several times since the mouse down event is detected through the transition. This has been fixed in SL2. In SL1, I needed to attach the triggers to an object and check to see if the object was visible before triggering the go. Spacing the object off the front of the timeline did the trick.
The other problem is when removing the triggers from the slide itself, the next flow is lost. No connectors, no flow. To get around this, I added a setup object to my slide that directed the next flow and contained a few other things. This way I could keep the navigation itself on the master slide and add the flow logic to the slide level. This provides the opportunity for branching logic that could jump outside of the linear flow based on certain conditions.
Don't have SL2 installed on my work machine yet. Here's an example of this in SL1.
There is some quirkiness with the layer > show master nav. There's a way to work around it but I don't remember exactly what it was.
I didn't update the slide titles but I've used a similar setup object for containing storyboard number. This is useful for tracking and feedback. One of the nice things about the setup object is that it's really easy to copy bundled triggers from one slide to another for varying navigation behaviors. These are also editable within Story View.
6 Replies
Hi Mike,
I haven't tried that recently so I may be wrong but, have you tried inserting your bar on a layer on the master slide? In most cases, that would appear on top of the base layer of a regular slide.
Cheers,
Alex
Yeah, I tried that, the View mode covers everything on the Master Slides from my experience.
I place navigation stuff on the master slide in a layer. A couple of sticky wickets you'll have to contend with.
I've done the same thing using a layer on the master slide pop up with some custom navigation options. There was one problem though that I couldn't get around. I had 5 buttons, Menu, Prev Scene, Prev Slide, Next Slide, Next Scene. The Menu, Prev Scene and Prev Slide worked, but not the Next Slide and Next Scene. I've tried different methods to try to make them work (even the increment trick) and they never went to the next slide or next scene.
My advice, is to some extensive testing before you go all out. Even though you really only have to make changes to one slide/layer, make sure it works before you get to a point where your entire course will rely on it.
One of the problems in SL1 was the next slide trigger will jump several times since the mouse down event is detected through the transition. This has been fixed in SL2. In SL1, I needed to attach the triggers to an object and check to see if the object was visible before triggering the go. Spacing the object off the front of the timeline did the trick.
The other problem is when removing the triggers from the slide itself, the next flow is lost. No connectors, no flow. To get around this, I added a setup object to my slide that directed the next flow and contained a few other things. This way I could keep the navigation itself on the master slide and add the flow logic to the slide level. This provides the opportunity for branching logic that could jump outside of the linear flow based on certain conditions.
Don't have SL2 installed on my work machine yet. Here's an example of this in SL1.
There is some quirkiness with the layer > show master nav. There's a way to work around it but I don't remember exactly what it was.
I didn't update the slide titles but I've used a similar setup object for containing storyboard number. This is useful for tracking and feedback. One of the nice things about the setup object is that it's really easy to copy bundled triggers from one slide to another for varying navigation behaviors. These are also editable within Story View.
This discussion is closed. You can start a new discussion or contact Articulate Support.