Forum Discussion
Help !
I can think of a few different possibilities. If you want people to return to the map before progressing to the final (seventh) sector, an automatic go-to could be triggered on the map slide when the timeline starts if the state of all six sector buttons is visited. Since the trigger is "when the timeline starts," it won't fire until the learner revisits the map after completing the sixth sector and returning to the map.
A slightly more accessible version would have a seventh button hidden on the map that only appears (again when the timeline starts) if the six buttons are all visited. That way learners won't be able to click it until they've returned to the menu from the sixth sector, but will still retain control of course and progress when they're ready. If your map has a visual theme (e.g., pirates) then I'm sure the seventh button can be "story"d in.
Ok I tried bth ways without sucess - I must be missing something I put a trigger on the button, hid it first then trigger to change state to normal when objects were visited
Hey - I have a relatively slow day and would like to help you, but I'm not 100% sure what you're asking. View the video file I posted and let me know. Once clarified, I'll be happy to help. https://www.toddweber.com/MAP01.mp4
It's really tough to say without seeing the project file, which I know you said you couldn't do. Maybe the trigger is being skipped or otherwise not run? Could be something hinky going on with the button states. Since the button for the final slide only appears if all of the sector buttons are in the visited state, maybe one of them is in another state?
Here's a quick implementation I cooked up just to show:
https://360.articulate.com/review/content/64614def-ffa3-45e4-81e4-17e20e42572e/review
If you're able/allowed to download external project files, it's available from this dropdown here if you didn't know:
My recommendation would be to move away from checking object states and try to use only variables. They're much less fickle and less prone to error. Each button would only need one additional, simple trigger:
And then the trigger that shows the final button would simply check each of those "visited" variables is true as opposed to checking the image state of each button.
I hope this works.
