Forum Discussion
Why does Scene 3 insist on showing up as Scene 4 in Scene 3s place?
I tried everything! But I cannot get Scene 4 to show up in Scene 4's place!!!!! But it shows up like it should in the menu. This is really frustrating!
11 Replies
- JudyNolletSuper Hero
Story View is programmed to represent the overall flow of a Storyline course. With a linear course, that's easy. When there's branching, it can get trickier. It interprets how scenes are interconnected. It might even be impacted by when and how inter-scene links are added.
Yes, it can be frustrating if it doesn't match how you would diagram the scenes. Fortunately, it doesn't impact how the course runs for the user.
- RonPricePartner
How are you triggering the items to jump to the Scenes from the first Slide? Are those triggers on Layers?
You can also check how your buttons appear top to bottom in the timeline. The scene connected to the button on the bottom of the timeline will always be on the far right. The scene connected to the button on the top will be on the left, etc.
If you reorder the stacking of the buttons . . . save . . .close and reopen Storyline, then it should reorder the scenes for you.
- JudyNolletSuper Hero
RonPrice: I'm glad you chimed in! I didn't realize the button's order on the timeline was related to how the scenes appear in Story View.
- RonPricePartner
It is one of those lesser known "features".
- CJLuCommunity Member
I'm not using buttons, but I am using hotspots over images with states. I have hotspots 1, 2, and 3, and they are all in order in the triggers panel and timeline. But still, the scenes do not align as they should. I have to add two more scenes. I hope this doesn't confuse things even more.
- JudyNolletSuper Hero
CJLu: This isn't about the Story View issue, but there is something that might simplify your programming.
You wrote:
I am using hotspots over images with states.
It sounds like the user needs to choose from among separate images.
If that's the case, why use hotspots at all? The action(s) that happen when the user clicks a hotspot (for example, jumping to a scene) could be triggered to run when the user clicks the image. That would let you take advantage of the automatic functionality that comes with using built-in states, such as the image automatically changing to the Selected state when clicked. And, if only one should be selected, you could put them in a button set. Or an image could automatically change to the Visited state.
Even if you don't need that automatic functionality, you'll still have fewer objects to deal with if they user can just click an image instead of a hotspot over an image.
For reference:
-
PRIMER: Take advantage of built-in states | E-Learning Heroes
-
https://www.articulatesupport.com/article/Storyline-360-Working-with-Button-Sets
-
PRIMER: Hotspots vs. Transparent Shapes | E-Learning Heroes (This is about using transparent shapes instead of hotspots, such as when multiple click areas need to be over a single image. It's just another option to consider.)
-
Related Content
- 1 month ago
- 2 months ago