I was sure that I had done this before, but I can't seem to get the Next and Previous buttons to appear after all of the 5 images on the screen are visited.
Here is what I have tried:
Using variables, it didn't work
Changing the State to "selected" instead of "visited" and that didn't work
Creating a Button Set, that didn't work
Changing the order of operations, that didn't work
Changing the slide state to "Resume saved state" that didn't work
I can't think of anything else! I'm ready to ask for help. I have attached the slide that is causing me so much grief. :-)
Ok, it's happening again. Maybe this is a bug. I thought I was just imagining things, but here I have the same problem and it's telling me that the Flagged objects do not have the selected state of "visited".
Later, if I try it again, it might work. Can you see anything wrong with the screenshot? I think the rectangles should have a visited state.
@Victoria: The screenshot indicates that the objects (rectanglexyz) do not have a Visited state and therefore you can't use that state in a trigger condition. Check the rectangles and add the Visited state.
Aha Thanks, Michael! I thought when they said those states were "built in" meant that I didn't need to add them. Much like I don't need to add the expressions on the characters' faces. I get it now - thanks!
Aha Thanks, Michael! I thought when they said those states were "built in" meant that I didn't need to add them. Much like I don't need to add the expressions on the characters' faces. I get it now - thanks!
Yes, only controls, such as buttons come with a full set of already-created, built-in states. For all other objects, like your rectangles, these states can easily be added but are not pre-built when you first insert a shape.
I saw on that page that they didn't make it clear (to me, anyway) that you have to add a visited state; they make it look like it's built-in. However, from this exercise, you can see you have to add it.
If you were adding in buttons they are sometimes included automatically - but you'll be able to use the behavior of the "visited" state even if you add it and label it as such.
After clicking all the triggers, getting the next button to show and going to the next slide, when I clicked previous, the hidden next button hides AGAIN and can't be triggered. Then all I could do is close the whole thing. I finally figured out to add a little something to the hide next button trigger. Was this the easiest thing to do?
Hi Deborah! It seems like that's a great idea as long as the slide is not set to return to initial state. Are you having difficulty with this setup or you were just looking for community feedback?
I guess I didn't understand why the returning to saved state didn't produce the Next button? I thought it might be a bug in the software OR in my brain?!?! I understand why my solution works but not why the default didn't.
Having the slide "resume to saved state" should work, assuming all the conditions you've outlined were already met as well. If you're having some difficulty with that, we'd be happy to take a look at the troublesome slide(s) to see how they are behaving and if there is anything else that could be impacting the set up.
Thanks Deborah - I rebuilt a similar set up, and I'm able to see that when revisiting the slide the next button is not staying as normal. I was able to get this working if I tracked it based on a variable associated with clicking the next button - so you could use that method, and I'll report the other behavior to our QA team.
Thanks for your patience as we investigate the issue associated with the next button not being normal/accessible on a revisit to a slide where you had initially set it to hidden at the start of the slide. It’s been determined that this behavior is as expected based on what the triggers are telling Storyline, although it may not match what you wanted to occur.
Since the previous/next buttons are set to be hidden at the start of the slide via triggers, when returning to the slide the command given to Storyline is to hide the buttons as soon as the slide starts. The slide is resuming the saved state of the previous/next buttons as expected, but then the triggers tell Storyline to hide them as soon as the slide loads.
This is where applying the conditions to those initial triggers will come into play - as you’ll want to adjust the next/previous buttons to “hidden” only if the user has not visited this slide before. You’ll see this set up in the file I attached that has that trigger/condition set up associated with the state change of the next player button.
Please let us know if you have any other questions!
I am facing this really weird problem right now. I have created a slide with lesson pictures and state changes. Every time the user is done with the lesson the state of that picture changes. I have hidden the next button. and created a simple trigger when the pictures are visited the next button changes to Normal.
When I preview just the slide the slide works perfectly. But when I preview the entire scene the next button remains hidden.
The scene contains several slides and layers within those slides. Anything i need to be checking for?
Hard to say without seeing the setup - is the slide with the lesson pictures is that a hub slide that jumps to other slides when the user clicks the picture or it jumps to layers of the slide?
Could it be the trigger order if it is not working when you are previewing entire project.
34 Replies
Hi Victoria,
I have solved your issue, and added two trigger to show PREV NEXT buttons. PFA. I hope given solution will be helpful for you.
Thank you both, Matthew and Ravindra!
I could have sworn I had done it that way one thousand times, Ravindra, but when I copied what you did, it worked perfectly!
Thank you so much!
Thank you, Matthew, I rearranged the order of the triggers, too. What you said makes total sense.
Thanks again!!!
Victoria
Ok, it's happening again. Maybe this is a bug. I thought I was just imagining things, but here I have the same problem and it's telling me that the Flagged objects do not have the selected state of "visited".
Later, if I try it again, it might work. Can you see anything wrong with the screenshot? I think the rectangles should have a visited state.
@Victoria: The screenshot indicates that the objects (rectanglexyz) do not have a Visited state and therefore you can't use that state in a trigger condition. Check the rectangles and add the Visited state.
Looks like Michael has popped in to assist you Victoria, just let us know if you need anything further.
Aha Thanks, Michael! I thought when they said those states were "built in" meant that I didn't need to add them. Much like I don't need to add the expressions on the characters' faces. I get it now - thanks!
Yes, only controls, such as buttons come with a full set of already-created, built-in states. For all other objects, like your rectangles, these states can easily be added but are not pre-built when you first insert a shape.
Hi Victoria,
You can read about all the built in states associated with buttons here.
Hope that helps!
That's great! Thank you, Ashley.
I saw on that page that they didn't make it clear (to me, anyway) that you have to add a visited state; they make it look like it's built-in. However, from this exercise, you can see you have to add it.
Hi Victoria,
If you were adding in buttons they are sometimes included automatically - but you'll be able to use the behavior of the "visited" state even if you add it and label it as such.
Hope that helps!
Thanks.
Just in case you want to go back to the slide:
After clicking all the triggers, getting the next button to show and going to the next slide, when I clicked previous, the hidden next button hides AGAIN and can't be triggered. Then all I could do is close the whole thing. I finally figured out to add a little something to the hide next button trigger. Was this the easiest thing to do?
Hi Deborah! It seems like that's a great idea as long as the slide is not set to return to initial state. Are you having difficulty with this setup or you were just looking for community feedback?
I guess I didn't understand why the returning to saved state didn't produce the Next button? I thought it might be a bug in the software OR in my brain?!?! I understand why my solution works but not why the default didn't.
Hi Deborah,
Having the slide "resume to saved state" should work, assuming all the conditions you've outlined were already met as well. If you're having some difficulty with that, we'd be happy to take a look at the troublesome slide(s) to see how they are behaving and if there is anything else that could be impacting the set up.
Thanks for responding so quickly!
Just go look at the file that Ravindra Gardi attached up above, "visitedstateproblem_Solved.story". It happens there also.
Thanks Deborah - I rebuilt a similar set up, and I'm able to see that when revisiting the slide the next button is not staying as normal. I was able to get this working if I tracked it based on a variable associated with clicking the next button - so you could use that method, and I'll report the other behavior to our QA team.
Thanks for listening.... I am not very versed on variables yet but you have encouraged me to "press on"!
No problem Deborah - and thanks for pressing on with this issue too. I'm glad I was able to share it with our QA team to investigate
Hi all,
Thanks for your patience as we investigate the issue associated with the next button not being normal/accessible on a revisit to a slide where you had initially set it to hidden at the start of the slide. It’s been determined that this behavior is as expected based on what the triggers are telling Storyline, although it may not match what you wanted to occur.
Since the previous/next buttons are set to be hidden at the start of the slide via triggers, when returning to the slide the command given to Storyline is to hide the buttons as soon as the slide starts. The slide is resuming the saved state of the previous/next buttons as expected, but then the triggers tell Storyline to hide them as soon as the slide loads.
This is where applying the conditions to those initial triggers will come into play - as you’ll want to adjust the next/previous buttons to “hidden” only if the user has not visited this slide before. You’ll see this set up in the file I attached that has that trigger/condition set up associated with the state change of the next player button.
Please let us know if you have any other questions!
Hi!
I am facing this really weird problem right now. I have created a slide with lesson pictures and state changes. Every time the user is done with the lesson the state of that picture changes.
I have hidden the next button. and created a simple trigger when the pictures are visited the next button changes to Normal.
When I preview just the slide the slide works perfectly. But when I preview the entire scene the next button remains hidden.
The scene contains several slides and layers within those slides. Anything i need to be checking for?
Unfortunately I cant share the file .
Hi Shubha
Hard to say without seeing the setup - is the slide with the lesson pictures is that a hub slide that jumps to other slides when the user clicks the picture or it jumps to layers of the slide?
Could it be the trigger order if it is not working when you are previewing entire project.
Hi Wendy,
I have a hub slide, on clicking the pictures it visits other slides which in turn have layers.
is the trigger to change the state of Next button to normal when timeline starts on hub slide on condition that pic1=visited and pic2= visited etc
and is the hub slide set to 'resume saved state'.
Wendy,
I'm attaching a sample file, with the Next button issue.
Do let me know what I'm doing wrong.
This discussion is closed. You can start a new discussion or contact Articulate Support.