I have 4 button list I want the user to select each and then after they have selected it and gone to the next screen, I have a back button to go to the list again but I want the button they chose to be unselectable after they have already selected it. How would I do that?
You could also just add a trigger that changes the button to Disabled when the button is clicked. That would have to come before the trigger that jumps to another slide.
However, I suggest you rethink disabling a button. Users could get frustrated if they can't revisit content. IMHO, it'd be better to use a Visited (or custom) state to indicate what content has already been viewed. But don't prevent someone from revisiting the content.
Good points, Judy. A much simpler way, and thanks for pointing out the issue with disabling buttons. I think it also can confuse a learner who might be wondering why they clicked it earlier, and it worked, but now it doesn't. It could create support calls as well when someone takes the course. The old saying, "Just because you can do something, doesn't mean you should." LOL
3 Replies
Jennifer,
One way to accomplish this is as follows:
1. Create a T/F variable and set its default value to False. For example, v_DisableButtons
2. Create triggers that set the state of each of the buttons to disabled when the timeline starts on the slide if v_DisableButtons = Value True
You could then set the state of the v_DisableButtons to True when the state of all of the buttons is visited.
Something like this. I'm sure there are other ways as well. With Storyline, there are always lots of ways to do things.
You could also just add a trigger that changes the button to Disabled when the button is clicked. That would have to come before the trigger that jumps to another slide.
However, I suggest you rethink disabling a button. Users could get frustrated if they can't revisit content. IMHO, it'd be better to use a Visited (or custom) state to indicate what content has already been viewed. But don't prevent someone from revisiting the content.
Good points, Judy. A much simpler way, and thanks for pointing out the issue with disabling buttons. I think it also can confuse a learner who might be wondering why they clicked it earlier, and it worked, but now it doesn't. It could create support calls as well when someone takes the course. The old saying, "Just because you can do something, doesn't mean you should." LOL
Richard