Sorry I did not even see that Spin Again icon on the layer, I thought you meant go back to the spinning wheel. See if the attached works for you. I have based it on the timeline ending on the layer and the condition that both hospitals are 'selected'. Also the group for clicking to get to the layer didn't have the layer assigned.
The Spin Again can have an initial state of hidden (do that via the states tab) then you don't need the initial 'change state of spin again to hidden when timeline starts' trigger.
I may have missed something in the previous posts but I did have a look at your original file. The Spin again button wasn't changed to Normal because the trigger to do that was attached to an object, rather than being a slide/layer trigger. See attached a revised file.
Leslie, the documentation at that link defines selected and visited states very similarly. Maybe you can clarify how "this is the how it appears when it is selected" is different to "this is how it appears when it is clicked". Isn't that the same thing?
Could you please explain how visited is different to selected?
Yes, I agree the two are very similar. If you read the descriptions, I think it's more important to note how it's handled subsequently once no longer the 'selected' item and that's when 'visited' comes into play.
Selected: This is how an object appears when it's been selected. It's generally used to indicate that a learner has chosen the object. For example, a check box uses the selected state to provide a visual cue (check mark), indicating it has been clicked.
Selected states are often used in conjuction with button sets, so only one object can be selected at a time.
If the selected state exists for an object, it'll automatically display when learners click it. You don't need to create a trigger to invoke it.
Visited: This is how an object appears after it has been clicked. It's useful when you want to provide learners with a visual indicator of the objects they've already clicked (for example, a series of buttons).
Storyline remembers this state when learners revisit the same slide later unless you've configured theslide properties or layer properties to "reset to initial state."
If the visited state exists for an object, it'll automatically display after learners click it. In other words, you don't need to create a trigger to invoke a visited state.
So to clarify, are you saying the difference is that if you select something, and then select something else, Storyline won't remember it has been selected (it loses its state), but with visited, it remembers it always? Is that correct?
Hey Victoria, here are some examples that may help that I've written up for someone in the past, but you are absolutely on the right track.
Selected State
Think about a light switch. When you turn a light switch on, then the light turns on. That's its "selected" state. When you turn the light switch off, it turns off again, it's now back to its "normal" state. When you turn the light switch on again, it's back to its lit "selected" state.
The selected state is helpful when you have multiple buttons, put them into a button set, and you only want them to be able to have one button "active" or "selected" at a time. (*This is what you're talking about above - when the user selects something else within the button set, then the previously selected button will lose its "selected" state.)
The "selected" state is most useful in a buttonset situation. E.g. tabs that you only want one open at a time, etc.
Another way to think about button sets with selected states is one of those pens that you can click down at the top to change colors.
Each color is a button in a button set. Every time you click a color down, the previously chosen color snaps back up to be replaced by the new color.
Now take that same light switch. It's off, in the "normal" state. You turn it on, the light comes on. But now when you try to switch it off again, it stays lit. This is similar to the "visited" state. The visited state is simply showing the user that they've already interacted with the object.
Using the same example as above with the multiple buttons, the user has clicked the first button and its in its "selected" state. The user clicks a different button in the button set, and the new button becomes "selected," and the previously selected button is now in its "visited" state. The "visited" state may be a different color (like gray) to indicate it's a button they've already interacted with.
You don't have to use "visited" with a button set, any screen at all with interactive objects can benefit from a "visited" state to show the user they have already clicked or interacted with the objects.
The visited state is also similar to clicking a link in a Word document or an email. The link turns purple, and it never turns back to blue again.
19 Replies
Hi Victoria
I added a visited state to both hospitals and then a trigger to hide the layer to go back to the spin wheel - hope that is what you meant.
Not exactly. I have a series of spin wheels - always advancing to the next one. So I want them to click the spin again button to go to the next one.
Can you tell me why the selected state wouldn't work with change state from hidden to normal?
I'm trying to understand why "change state of X when the state of both y and z are selected" doesn't work.
It seems to me it should.
Thanks!
Sorry I did not even see that Spin Again icon on the layer, I thought you meant go back to the spinning wheel. See if the attached works for you. I have based it on the timeline ending on the layer and the condition that both hospitals are 'selected'. Also the group for clicking to get to the layer didn't have the layer assigned.
The Spin Again can have an initial state of hidden (do that via the states tab) then you don't need the initial 'change state of spin again to hidden when timeline starts' trigger.
Hi Victoria! Looks like you are getting some great assistance from Wendy here :)
Yes, Wendy is being a great help, but I would still like to know, Leslie, whether lightboxes interfere with interactions or not?
Yes, the group was assigned, but the whole interaction was too large to post, so I deleted a whole bunch of layers.
Yes, good idea about the hidden state. I thought maybe that's why it wasn't working, so I changed it.
I still don't understand why the initial setup didn't work.
If I have the spin again button changing to normal when the 2 hospitals are in the selected state- that should work, right?
I may have missed something in the previous posts but I did have a look at your original file. The Spin again button wasn't changed to Normal because the trigger to do that was attached to an object, rather than being a slide/layer trigger. See attached a revised file.
Great suggestion, Michael! Please let us know if that does the trick for you, Victoria, or if you still need additional assistance. :)
Ok, this is weird. Nothing worked, so I deleted the "selected" state and replaced it with a "visited" state and it worked.
I wonder what the differences are between the selected and visited - ????? Does anyone know, from a behavioural perspective?
Thank you, community for helping me!
Hi Victoria
here is a definition of the built in states - hope this helps.
http://en-au.articulate.com/support/storyline-2/definition-of-built-in-states-sl2
Hi Victoria! Looks like Wendy popped in with the documentation :)
Thank you for all of your help, Wendy!
Leslie, the documentation at that link defines selected and visited states very similarly. Maybe you can clarify how "this is the how it appears when it is selected" is different to "this is how it appears when it is clicked". Isn't that the same thing?
Could you please explain how visited is different to selected?
Hi Victoria!
Yes, I agree the two are very similar. If you read the descriptions, I think it's more important to note how it's handled subsequently once no longer the 'selected' item and that's when 'visited' comes into play.
Selected states are often used in conjuction with button sets, so only one object can be selected at a time.
If the selected state exists for an object, it'll automatically display when learners click it. You don't need to create a trigger to invoke it.
Storyline remembers this state when learners revisit the same slide later unless you've configured theslide properties or layer properties to "reset to initial state."
If the visited state exists for an object, it'll automatically display after learners click it. In other words, you don't need to create a trigger to invoke a visited state.
Thanks Leslie. I did read that.
So to clarify, are you saying the difference is that if you select something, and then select something else, Storyline won't remember it has been selected (it loses its state), but with visited, it remembers it always? Is that correct?
Hey Victoria, here are some examples that may help that I've written up for someone in the past, but you are absolutely on the right track.
Selected State
Think about a light switch. When you turn a light switch on, then the light turns on. That's its "selected" state. When you turn the light switch off, it turns off again, it's now back to its "normal" state. When you turn the light switch on again, it's back to its lit "selected" state.
The selected state is helpful when you have multiple buttons, put them into a button set, and you only want them to be able to have one button "active" or "selected" at a time. (*This is what you're talking about above - when the user selects something else within the button set, then the previously selected button will lose its "selected" state.)
The "selected" state is most useful in a button set situation. E.g. tabs that you only want one open at a time, etc.
Another way to think about button sets with selected states is one of those pens that you can click down at the top to change colors.
Each color is a button in a button set. Every time you click a color down, the previously chosen color snaps back up to be replaced by the new color.
Articulate article about button sets: https://community.articulate.com/series/5/articles/adding-button-sets
Visited State
Now take that same light switch. It's off, in the "normal" state. You turn it on, the light comes on. But now when you try to switch it off again, it stays lit. This is similar to the "visited" state. The visited state is simply showing the user that they've already interacted with the object.
Using the same example as above with the multiple buttons, the user has clicked the first button and its in its "selected" state. The user clicks a different button in the button set, and the new button becomes "selected," and the previously selected button is now in its "visited" state. The "visited" state may be a different color (like gray) to indicate it's a button they've already interacted with.
You don't have to use "visited" with a button set, any screen at all with interactive objects can benefit from a "visited" state to show the user they have already clicked or interacted with the objects.
The visited state is also similar to clicking a link in a Word document or an email. The link turns purple, and it never turns back to blue again.
Anyways - hopefully those examples helped.
Thank you, Rachel! That is excellent, and exactly what I was looking for.
Much appreciated!!
Excellent news, Victoria! Delighted to see that Rachel was able to give you what you needed. We appreciate the update. :)
Love that explanation Rachel and very glad that it was able to assist you Victoria :)
This discussion is closed. You can start a new discussion or contact Articulate Support.