Good morning. I hope you all had a nice Thanksgiving.
I'm trying to use the built-in states for hover and visited for a menu slide, but I'd like to disable these states until they finish each previous section. It seems that those states are enabled by default. It seems like I need a trigger that will save change state to hover (and let the button be clickable) only if they visited X slide.
For the button to be accessible, does this make sense? I add a variable to the jump to trigger like this: Jump to slide 2.3 when user clicks Button 5 if Button Intro equals to visited. Do you see any problems with this?
Also, I thought that buttons they can't click on yet (out of sequence) shouldn't have the hover state yet, but I can't figure out how to disable it.
Hover and Visited are built-in states which are automatically displayed. Have you tried initially showing the buttons in Disabled state until the previous section is completed?
I think you can disable a button (by setting its state to disable or hidden), and you can reverse that condition, but I don't think you can selectively disable one of the built-in states.
It seems to me that there is a reasonable large cohort of people that are not happy with the way the built-in states of normal, selected, visited and hover interact. Specifically, once a state turns to hover, there is no indication of whether the object has already been visited or selected.
I have found that if you use a button to branch to another section of the project which contains a large number of slides, or another branching option, the visited state is not consistently reliable.
Thank you both for your thoughts. I really appreciate it.
I removed the hover and visited states. I created a complete state and used a true/false variable to get it to change states. That's working fine. I'm not going to worry about hover for now.
I tested one button with Disabled with this trigger: Change state of Button 5 to Disabled when the timeline starts if Introcomplete (variable) is False (which is its initial variable setup). That is working, it appears. Then I created a second trigger: Change state of Button 5 to Normal when the timeline starts if Introcomplete is True. I ran through the slides that would trigger the variable to change to True, and that's not working. Any thoughts on how to work with the Disabled state are very much appreciated. Tks!
I don't know if this helps at all, but here is an example of a menu where sections have to be completed in sequence and the related menu buttons are enabled one after the other. If this is what you're after, let me know and I upload the .story file.
That is exactly what I want to do! I would love to see how you set that up if you're willing. What I ended up doing was using hotspots and variables, and it's working just as yours is set up. I feel like I'm doing everything the hard way right now.
11 Replies
Hover and Visited are built-in states which are automatically displayed. Have you tried initially showing the buttons in Disabled state until the previous section is completed?
My thoughts:
I think you can disable a button (by setting its state to disable or hidden), and you can reverse that condition, but I don't think you can selectively disable one of the built-in states.
It seems to me that there is a reasonable large cohort of people that are not happy with the way the built-in states of normal, selected, visited and hover interact. Specifically, once a state turns to hover, there is no indication of whether the object has already been visited or selected.
I have found that if you use a button to branch to another section of the project which contains a large number of slides, or another branching option, the visited state is not consistently reliable.
Thank you both for your thoughts. I really appreciate it.
I removed the hover and visited states. I created a complete state and used a true/false variable to get it to change states. That's working fine. I'm not going to worry about hover for now.
I tested one button with Disabled with this trigger: Change state of Button 5 to Disabled when the timeline starts if Introcomplete (variable) is False (which is its initial variable setup). That is working, it appears. Then I created a second trigger: Change state of Button 5 to Normal when the timeline starts if Introcomplete is True. I ran through the slides that would trigger the variable to change to True, and that's not working. Any thoughts on how to work with the Disabled state are very much appreciated. Tks!
I don't know if this helps at all, but here is an example of a menu where sections have to be completed in sequence and the related menu buttons are enabled one after the other. If this is what you're after, let me know and I upload the .story file.
That is exactly what I want to do! I would love to see how you set that up if you're willing. What I ended up doing was using hotspots and variables, and it's working just as yours is set up. I feel like I'm doing everything the hard way right now.
Thank you so much, Michael.
See attached the .story file.
That is awesome. I can't thank you enough. Thank you!!
If you are still interested, here is one button with both visited and hover states, and another with both hover and selected.
The hover and visited states are custom, but I use the built-in selected state, because it seems pretty reliable.
That's very interesting, Walt. Thank you so much for sharing. I couldn't see the visited states anywhere, but clearly they're there and working.
Thanks!
Actually, there are two buttons. The selected is hidden until the user visits, then it changes to normal, and the other one changes to hidden.
I've got it now. Why does some of this seem so complicated at times! Thanks, Walt.
This discussion is closed. You can start a new discussion or contact Articulate Support.