I am not sure how to explain what I want to do. Hope you understand me. I create in Storyline a menu where you have to click each box to review a topic. Every box jumps the reader to the topic and that is working perfect, but I want to force the reader to view the topics in a particular order.
I though I saw something like a lock to prevent him to jump or use other boxes until he finish the first one, or the second, etc, but I cant seem to find it.
You can achieve this in a few ways. One of which is through states. You can set the boxes that jump to each topic to an initial state of Disabled. Then have a trigger to change them to Normal state upon timeline start if the box prior to it is in a Visited state.
Do you have a file to share that we can add some trigger to the setup?
Maybe the attached file gives you some ideas. It forces the user to complete sections in a specific order. Otherwise, post your .story file her for us to have a closer look.
Your file solved the original problem with a good solution. I have a scenario very similar to the original post, but here's my twist.
Each of my topics has multiple screens. Once users are back to the main menu, I don’t want them to be able to revisit a topic they’ve already viewed. Is this something you can advise me on? I hate to ask, but my experience with conditions & variations is severely limited.
I’m sending back your original story file (that self-updated to the current software version when I opened it). I added my initials to the end. I added clickable boxes that jump back to the main menu on the surface of the screens because my client never navigates with player menus, only swipes and taps.
Is this achievable? You helped me very recently with a problem and I greatly appreciated the support.
Maybe this is too simplistic, but have a look at the attached. I revised the logic for topic 1 as follows:
1. On the Topic 1 screen (this should be the last screen in for this topic if you have more than one), I set a True/False variable to True to signify completion of this topic.
2. On the Menu slide, I added triggers that change the state of the topic 1 button to disabled, if the variable is true. That makes sure that topic 1 (once complete) cannot be accessed again. I also added a trigger to enable the topic 2 button if the variable is True. This 'unlockes' the next topic.
Hopefully, you can replicate this approach for the other menu items.
Thanks Michael, I'll work with this adding more content. The logic looks right to me but I think I need to add more screens and work with this before it sinks in.
Would jumping to different scenes work in a similar way but keep my story views easier to see at a glance? I think there will be 3 screens in each topic. I'd also create a results slide to track or report the quiz from each topic.
Yes, I would create separate scenes for each topic. Remember to set the True/False variable for each topic to true on the last slide of a scene. If you get stuck you can always share your .story file and someone will have a look.
6 Replies
Hello Angela,
You can achieve this in a few ways. One of which is through states. You can set the boxes that jump to each topic to an initial state of Disabled. Then have a trigger to change them to Normal state upon timeline start if the box prior to it is in a Visited state.
Do you have a file to share that we can add some trigger to the setup?
Maybe the attached file gives you some ideas. It forces the user to complete sections in a specific order. Otherwise, post your .story file her for us to have a closer look.
Hi Michael,
Your file solved the original problem with a good solution. I have a scenario very similar to the original post, but here's my twist.
Each of my topics has multiple screens. Once users are back to the main menu, I don’t want them to be able to revisit a topic they’ve already viewed. Is this something you can advise me on? I hate to ask, but my experience with conditions & variations is severely limited.
I’m sending back your original story file (that self-updated to the current software version when I opened it). I added my initials to the end. I added clickable boxes that jump back to the main menu on the surface of the screens because my client never navigates with player menus, only swipes and taps.
Is this achievable? You helped me very recently with a problem and I greatly appreciated the support.
Maybe this is too simplistic, but have a look at the attached. I revised the logic for topic 1 as follows:
1. On the Topic 1 screen (this should be the last screen in for this topic if you have more than one), I set a True/False variable to True to signify completion of this topic.
2. On the Menu slide, I added triggers that change the state of the topic 1 button to disabled, if the variable is true. That makes sure that topic 1 (once complete) cannot be accessed again. I also added a trigger to enable the topic 2 button if the variable is True. This 'unlockes' the next topic.
Hopefully, you can replicate this approach for the other menu items.
Thanks Michael, I'll work with this adding more content. The logic looks right to me but I think I need to add more screens and work with this before it sinks in.
Would jumping to different scenes work in a similar way but keep my story views easier to see at a glance? I think there will be 3 screens in each topic. I'd also create a results slide to track or report the quiz from each topic.
Yes, I would create separate scenes for each topic. Remember to set the True/False variable for each topic to true on the last slide of a scene. If you get stuck you can always share your .story file and someone will have a look.
This discussion is closed. You can start a new discussion or contact Articulate Support.