Need Some Clarification About Selected Vs Visited States

Hi Everyone

I am possibly just not understanding something here, but I can't seem to get selected and visited states to work correctly if I have an asset that makes use of both of them. 

The .story file attached is very simple. It has three boxes.

  1. The first box has three states: Normal (a blue box with 'Normal' written beside it), Selected (an orange box with 'Selected' written beside it), and Visited (the same blue box as normal with 'Visited' beside it).
  2. The second box is as above but without the text by the side. 
  3. The third box is a replica of the first.

When I select box one, I would expect it to change to its Selected state (orange box with selected in front). But while it changes the blue box to orange, the text elements from both the Selected and Visited states are present. Indeed the 'Visited' text seems to be dominant as it appears on top of that of 'Selected. (FYI - all text was written when I was editing the state, not on the slide, which is why it can't be changed unless you are editing the state directly.)

I then select box two, and I would expect box one to change to the Visited state (blue box with 'Visited' written beside it). However, the orange box remains, with the overlapping text in place. Box two changes to the orange Selected state as expected, but when I then select box three, it remains fixed at the Selected state rather than changing to the Visited blue box. 

I appreciate that you can put in triggers to manually change the states, but as these are built-in, I would have thought that we shouldn't need to do that. 

Am I completely missing something? 

7 Replies
Nancy Woinoski

I don't think you are missing anything James. I think this is a bug. I noticed the same type of thing on the project I am working on right now.

I have an shape with a text question mark on the normal state - when users selects the shape it is supposed to change the text but I notice the question mark still remains underneath.  I have not reported the bug yet but plan to do so now that I see it is not just something that I was doing wrong.

I wonder what would happen if you made the text graphics instead?  You shouldn't have to do this but if it is just a text issue maybe using graphics will solve the problem in the meantime.

James McLuckie

Thanks for the reply, Nancy. Am glad that you've clarified that this is a bug. 

Next thing, I guess, is to establish if I am fundamentally misunderstanding what should happen if you have a Normal>Selected>Visited trigger suite set up. I have put together another slide, with the text input as a graphic directly on top of the box. Again, there are three boxes, each with a Normal, Selected and Visited state. 

When I select box one, it reverts to Selected. That's fine. When I select box two, it also changes to Selected. Again  fine, But because this is now the assetthat I have selected, my expectation would be that box one should then change to visited, because it is no longer the thing that I have selected. However, it stay as Selected.

Again, I know I could put a trigger in there to manually change it, but I just wanted to be clear on how it works. Thank again, Nancy.

Phil Mayor

James McLuckie said:

Thanks for the reply, Nancy. Am glad that you've clarified that this is a bug. 

Next thing, I guess, is to establish if I am fundamentally misunderstanding what should happen if you have a Normal>Selected>Visited trigger suite set up. I have put together another slide, with the text input as a graphic directly on top of the box. Again, there are three boxes, each with a Normal, Selected and Visited state. 

When I select box one, it reverts to Selected. That's fine. When I select box two, it also changes to Selected. Again  fine, But because this is now the assetthat I have selected, my expectation would be that box one should then change to visited, because it is no longer the thing that I have selected. However, it stay as Selected.


You need to set all the buttons up as a button set, which will ensure only one can be selected.

The other is odd and can sometimes be different based on which states you create first.

E.g normalVisited/Selected sometimes behaves differently to normal/selected/visited.

James McLuckie

Thanks, Phil. But could I trouble you to clarify what exactly you mean by a "button set"? In the particular instance of the file above, the "buttons" are actually graphics that I have build in Storyline and imported. If I have used the "Edit States" faciility to set these graphics up as "Visited", "Selected" etc. does that not count as a button set? 

When I use states I often don't intended them to act as "buttons" necessarily, but as graphics that react a certain way depending on the choices a learner makes.