So one of my pages has 4 layers. I want the user to click next to go to each layer, but some reason it states suck on the 2nd layer and does not go to the next two. I have reordered them in the player triggers, but still no luck. What am I doing wrong? Do I also need to include a variable?
Just wanted to follow up to make sure that putting your different slide layers on their own new slides instead is working for you. Having four different triggers attached to the same next button can get messy.
Technically, what you want to do is possible. However, you'd need to program some logic in.
You see, when you press the next button, all of those triggers you have are going to fire (in order from top to bottom). Also, each of your layers is set to "hide other layers". This is why it appears to get "stuck". The triggers are each executing and, in this case, hiding the previous layer that was shown (we don't actually see it as it happens so fast). Hence, the last trigger to be fired causes that last layer to be shown. Using some True False variables, you could get the logic worked out by adding in some conditions. However, Peter's approach is much easier and less labor intensive!
7 Replies
Hey Nadine!
Are you able to attach the .story file, or send it over privately, so we can have a look at it?
Can seem to attach it privately so here you go....
Thanks, Nadine
We'll take a look now...
Hi Nadine,
Just wanted to follow up to make sure that putting your different slide layers on their own new slides instead is working for you. Having four different triggers attached to the same next button can get messy.
Let us know how it's going...
Thanks!
Thanks Peter, works ok as different slides instead of layers
Cool, glad to hear it
Good luck with the rest of the project!
Nadine,
Technically, what you want to do is possible. However, you'd need to program some logic in.
You see, when you press the next button, all of those triggers you have are going to fire (in order from top to bottom). Also, each of your layers is set to "hide other layers". This is why it appears to get "stuck". The triggers are each executing and, in this case, hiding the previous layer that was shown (we don't actually see it as it happens so fast). Hence, the last trigger to be fired causes that last layer to be shown. Using some True False variables, you could get the logic worked out by adding in some conditions. However, Peter's approach is much easier and less labor intensive!
Mike
This discussion is closed. You can start a new discussion or contact Articulate Support.