I am wondering if I am missing something obvious. I have set a nav bar on my master slide. Then I want the user to be able to click to show a larger nav bar. Everything works fine except the next button on the master slide layer. The back button works fine, just the next. I tried assigning the trigger to objects/text/pictures with no luck.
I tried searching this but couldn't find anything quite like this. Seems like a weird bug that other commands would work (back or jump to specific slide).
I have uploaded the source file. Any help is much appreciated.
1) You have two slide named "Slide 2" you need to fix that
2) When you are in your third slide there is nowhere else to go :( you can change that by selecting that in "Player Triggers" on the right menu. Open your last slide. Then, double click on "Jump to next slide" and select where you want to go back
3) If you prefer to use your own button then you can unable the one from the layout. Go to Storyline view click on each slide and on the right menu deselect Prev, Next and Submit buttons.
I think your buttons are working fine is just the last next button does not know where is the next slide you want to go. Good luck!!!
The file is attached again - do you need more than the .story file?
@Erika, thanks for your suggestions. I am not sure that your suggestions will actually solve the issue.
1. I don't think the slide name really matters since I technically have "1.2 Slide 2" and "1.3 Slide 2". Just in case I renamed in the new file.
2. The issue isn't just on the third slide - in all slides the next button on the layer (green buttons) doesn't work. i.e., you can't advance to the next slide using any of the big green next buttons. Curiously, the green back buttons work just fine.
3. When I have got the buttons worked out, I'll remove the player buttons.
There are some really weird restrictions within layers on the master slide. I think this is more of a bug than anything but it's something that's been there since release. There are a few workarounds to this. I use a couple of proxies to transmit changes to the master slide or to the base slide.
See the attachment. I moved your layer down to the blank layout. I'm using a shape on the base of the master slide to catch state changes from the layer button. I then use a "listener" to trigger the jump to next slide when the trigger sees a change in the state.
I've also done this with a variable. Adding a 1 to a variable is a nice way to transmit a button event from the master to a the base slide. That way you can modify the slide jump destination on a per slide basis.
I was incredibly confused when I read your post and then dug into the file and it seems like a brilliant work around. I agree that the way I did it not working seems like it must be more of a bug than anything else.
This will work for now (and I would not have thought of that myself) - THANKS!
There are some really weird restrictions within layers on the master slide. I think this is more of a bug than anything but it's something that's been there since release. There are a few workarounds to this. I use a couple of proxies to transmit changes to the master slide or to the base slide.
See the attachment. I moved your layer down to the blank layout. I'm using a shape on the base of the master slide to catch state changes from the layer button. I then use a "listener" to trigger the jump to next slide when the trigger sees a change in the state.
I've also done this with a variable. Adding a 1 to a variable is a nice way to transmit a button event from the master to a the base slide. That way you can modify the slide jump destination on a per slide basis.
There are some really weird restrictions within layers on the master slide. I think this is more of a bug than anything but it's something that's been there since release. There are a few workarounds to this. I use a couple of proxies to transmit changes to the master slide or to the base slide.
See the attachment. I moved your layer down to the blank layout. I'm using a shape on the base of the master slide to catch state changes from the layer button. I then use a "listener" to trigger the jump to next slide when the trigger sees a change in the state.
I've also done this with a variable. Adding a 1 to a variable is a nice way to transmit a button event from the master to a the base slide. That way you can modify the slide jump destination on a per slide basis.
8 Replies
Hey Steve,
Mind uploading and sharing your file with our support team so they can take a look?
Hi Steve,
I have seen your project ok here are some tips:
1) You have two slide named "Slide 2" you need to fix that
2) When you are in your third slide there is nowhere else to go :( you can change that by selecting that in "Player Triggers" on the right menu. Open your last slide. Then, double click on "Jump to next slide" and select where you want to go back
3) If you prefer to use your own button then you can unable the one from the layout. Go to Storyline view click on each slide and on the right menu deselect Prev, Next and Submit buttons.
I think your buttons are working fine is just the last next button does not know where is the next slide you want to go. Good luck!!!
EM
Hi Peter,
The file is attached again - do you need more than the .story file?
@Erika, thanks for your suggestions. I am not sure that your suggestions will actually solve the issue.
1. I don't think the slide name really matters since I technically have "1.2 Slide 2" and "1.3 Slide 2". Just in case I renamed in the new file.
2. The issue isn't just on the third slide - in all slides the next button on the layer (green buttons) doesn't work. i.e., you can't advance to the next slide using any of the big green next buttons. Curiously, the green back buttons work just fine.
3. When I have got the buttons worked out, I'll remove the player buttons.
Thanks for the tips.
Steve
Sorry Peter, didn't see that your upload was a link for a support case. Uploading now.
Hi, Steve -
There are some really weird restrictions within layers on the master slide. I think this is more of a bug than anything but it's something that's been there since release. There are a few workarounds to this. I use a couple of proxies to transmit changes to the master slide or to the base slide.
See the attachment. I moved your layer down to the blank layout. I'm using a shape on the base of the master slide to catch state changes from the layer button. I then use a "listener" to trigger the jump to next slide when the trigger sees a change in the state.
I've also done this with a variable. Adding a 1 to a variable is a nice way to transmit a button event from the master to a the base slide. That way you can modify the slide jump destination on a per slide basis.
Hi Steve,
I was incredibly confused when I read your post and then dug into the file and it seems like a brilliant work around. I agree that the way I did it not working seems like it must be more of a bug than anything else.
This will work for now (and I would not have thought of that myself) - THANKS!
S
This discussion is closed. You can start a new discussion or contact Articulate Support.