Can anyone tell me how I can have the user click only the next button to advance through multiple layers. For example, I have 4 text boxes and want them to appear one at a time whenever the user click NEXT. I am struggling.
You might be able to accomplish this by using variables. Every time the user clicks the next button, you could have the variable advance by "x". Then your layer transition could be based on your variable count.
You would also have to add a condition to the next button, as to not advance to the next slide until the variable is => than "y".
John, I haven't tried your resolution - I was off thinking in a different direction already. Dan, if you try it, let us know how it works.
My "direction" involved using a custom next button instead of the default one. That may not be what you want, but just if it will work for you, take a look at this story.
I've removed the built-in next button by clicking the little gear icon on the bottom right of the slide layers area and removing the checkmark from the Next checkbox in the Slide Properties dialog box.
Then I inserted buttons on the base layer and on the other layers. Each button includes a trigger that "jumps" to the next layer and finally the next slide when clicked.
If you can't use a custom next button, let us know if John's solution works.
I saw you post in the past. I am just trying to do avoid multiple buttons to advance layers. I have a simple slide where the user clicks the next button to bring in the next layer (not go to the next slide until all the layers appear). Do you think give me a step by step or could call me to explain the variable? Thanks, Dan
The "built-in" Next button that is part of the player GUI will only advance forward to the next slide, not slide layer, I'm pretty sure.
One question I usually end up asking myself in situations like this is does it make sense for my content to be built as slide layers if this is the way I need the Next button to function? One option would definitely be to break your slide layers out into individual slides...
I don't know why but I often find myself debating when is it best to use slide layers vs individual slides. Might be nice to see some best practices put together for consideration in these situations.
A little out of my league. I ended up just making a big transparent button over each the entire screen so the user can click anywhere on the slide to advance to the next layer. I took out the player altogether. Working really well.
You should watch a couple of tutorials on variables and conditions. They are not really that bad once you get into them, and they open up many possibilities within Articulate.
The "built-in" Next button that is part of the player GUI will only advance forward to the next slide, not slide layer, I'm pretty sure.
You can make the next button show a layer, but unless you do what John did, it will only work on that one layer.
I never considered what John did, but that's a very simple obvious work around.
Someday, I'm going to start thinking variables quicker than I do right now. As it stands, I usually have to be smacked in the face with how obvious an answer those are.
13 Replies
You might be able to accomplish this by using variables. Every time the user clicks the next button, you could have the variable advance by "x". Then your layer transition could be based on your variable count.
You would also have to add a condition to the next button, as to not advance to the next slide until the variable is => than "y".
I hope that makes sense.
Hi Guys,
John, I haven't tried your resolution - I was off thinking in a different direction already. Dan, if you try it, let us know how it works.
My "direction" involved using a custom next button instead of the default one. That may not be what you want, but just if it will work for you, take a look at this story.
I've removed the built-in next button by clicking the little gear icon on the bottom right of the slide layers area and removing the checkmark from the Next checkbox in the Slide Properties dialog box.
Then I inserted buttons on the base layer and on the other layers. Each button includes a trigger that "jumps" to the next layer and finally the next slide when clicked.
If you can't use a custom next button, let us know if John's solution works.
I saw you post in the past. I am just trying to do avoid multiple buttons to advance layers. I have a simple slide where the user clicks the next button to bring in the next layer (not go to the next slide until all the layers appear). Do you think give me a step by step or could call me to explain the variable? Thanks, Dan
Hi Rebecca, I see what you are doing, that was my next thought. I think that might be the easiest. Thanks, Dan
Try this... I created a variable that increases by one every time the next button is pressed. I then set triggers with conditions for each layer.
The "built-in" Next button that is part of the player GUI will only advance forward to the next slide, not slide layer, I'm pretty sure.
One question I usually end up asking myself in situations like this is does it make sense for my content to be built as slide layers if this is the way I need the Next button to function? One option would definitely be to break your slide layers out into individual slides...
I don't know why but I often find myself debating when is it best to use slide layers vs individual slides. Might be nice to see some best practices put together for consideration in these situations.
Dan,
I left out one trigger in that picture.
You will also need one that states as follows. "Jump to next slide when the user clicks the next button if the countingthenextbutton...is equal to 4".
It works great for me. I am glad you brought it up, I will use that in the future!!
Nice workaround John
A lot of work but VERY cool, John!
Thanks John,
A little out of my league. I ended up just making a big transparent button over each the entire screen so the user can click anywhere on the slide to advance to the next layer. I took out the player altogether. Working really well.
Dan,
You should watch a couple of tutorials on variables and conditions. They are not really that bad once you get into them, and they open up many possibilities within Articulate.
You can make the next button show a layer, but unless you do what John did, it will only work on that one layer.
I never considered what John did, but that's a very simple obvious work around.
Someday, I'm going to start thinking variables quicker than I do right now. As it stands, I usually have to be smacked in the face with how obvious an answer those are.
Awesome John, works perfectly. The Next button dependent variable opens up a lot of possibility.
This discussion is closed. You can start a new discussion or contact Articulate Support.