...pretty much what the title says; I have 3 text boxes on my home slide that a user can click on. Once they click on the first text box, it disappears when they return back to the home slide. Strangely enough, the other 2 text boxes can be clicked on and don't disappear on return. They all have the same trigger behaviours, so I don't know what could be causing this. Does anyone have any ideas?
Yeah, it's a little difficult to explain, but I'll try.
My home page has 3 text boxes. Each text box, when clicked, takes the user to a different slide. When the user's finished, they go back to the home page, where they should see all 3 text boxes again.
If you click on text boxes 2 or 3, they work as expected - they take the user to the correct slides, and when the user returns to the home slide, the text boxes are still there where they should be.
However, if you click on text box 1, it takes the user to the correct slide, but when they come back to the home slide, text box 1 had disappeared.
Without seeing the file it's difficult to say - but I'd check that it didn't have any states associated with it where the text box is being hidden. Hidden is a built in state, but you may have also inadvertently edited the "visited" state for example to remove the text box and then it would be missing on the slide. Additionally, it's always a good reminder to confirm that you're working on project files as described here.
If you want to upload the file using the "add attachment" button we'll be happy to take a look at what's occurring and see if we can spot anything else. Additionally you are always welcome to share a file with our Support engineers by sending it along to us here.
It could be something to do with the timeline... maybe the first text box doesn't reach the end? It might be that your slide properties need to be set to the initial state when you return to the slide. It might be something funny in a trigger.
Check out the attached .story file. I duplicated your selected state and made it "Visited". Also, for text box 1, I removed the triggers you had for "Hover" and "Selected".
The nice thing about Storyline is if you add hover, selected and visited states Storyline automagically handles the rest, no need to add triggers.
By adding a "visited" state you will automatically see the visited state when the user returns to the slide.
Glad to help! I would set the other two boxes up the same way as text box 1. You can customize the visited state to change the text color if you want, or even do something like add a check mark, etc., to help the user see they've already visited that section.
My experience is that it sometimes confuses storyline to add triggers for the built in states (normal, hover, selected, visited), and that things generally work smoother if you let Storyline handle the heavy lifting as far as using the built in states go.
The only exception is when you add custom states and need to adjust them based on a variable, or if you need to adjust the state of one object while hovering or selecting another, etc.
9 Replies
Hi Jon,
Any way you can share an example of the issue you're experiencing?
Hi Jon,
It could be a number of things, but like Brian suggested, I think the easiest way to figure this one out will be to look at the slide. :)
Yeah, it's a little difficult to explain, but I'll try.
My home page has 3 text boxes. Each text box, when clicked, takes the user to a different slide. When the user's finished, they go back to the home page, where they should see all 3 text boxes again.
If you click on text boxes 2 or 3, they work as expected - they take the user to the correct slides, and when the user returns to the home slide, the text boxes are still there where they should be.
However, if you click on text box 1, it takes the user to the correct slide, but when they come back to the home slide, text box 1 had disappeared.
Any ideas?
Hi Jon,
Without seeing the file it's difficult to say - but I'd check that it didn't have any states associated with it where the text box is being hidden. Hidden is a built in state, but you may have also inadvertently edited the "visited" state for example to remove the text box and then it would be missing on the slide. Additionally, it's always a good reminder to confirm that you're working on project files as described here.
If you want to upload the file using the "add attachment" button we'll be happy to take a look at what's occurring and see if we can spot anything else. Additionally you are always welcome to share a file with our Support engineers by sending it along to us here.
Here is the published story. The slide in question is the second one.
Hi Jon,
It could be something to do with the timeline... maybe the first text box doesn't reach the end?
It might be that your slide properties need to be set to the initial state when you return to the slide.
It might be something funny in a trigger.
These are just guesses though :)
Jon,
Check out the attached .story file. I duplicated your selected state and made it "Visited". Also, for text box 1, I removed the triggers you had for "Hover" and "Selected".
The nice thing about Storyline is if you add hover, selected and visited states Storyline automagically handles the rest, no need to add triggers.
By adding a "visited" state you will automatically see the visited state when the user returns to the slide.
Hope this helps!
That did it! Thanks very much. So is that what I was doing wrong? I did the same for all 3 text boxes.
Glad to help! I would set the other two boxes up the same way as text box 1. You can customize the visited state to change the text color if you want, or even do something like add a check mark, etc., to help the user see they've already visited that section.
My experience is that it sometimes confuses storyline to add triggers for the built in states (normal, hover, selected, visited), and that things generally work smoother if you let Storyline handle the heavy lifting as far as using the built in states go.
The only exception is when you add custom states and need to adjust them based on a variable, or if you need to adjust the state of one object while hovering or selecting another, etc.
This discussion is closed. You can start a new discussion or contact Articulate Support.