Forum Discussion
Condition on Hotspots for an Order
To make this easier I'm supplying you my test .story file. I've tweaked the code a little and there are 2 slides. One where you can only go up, and not back. and another where you can go up (still can't skip a hotspot) but you can also revisit previous layers.
Reach out if you have any questions.
Ron's solution definitely works if you're building all the layers onto the slide (that is, not hiding the current layer when a new layer is shown).
Phil's solution works in more situations. Any triggers you'd add to a hotspot can be added to a shape filled with a color set to 100% transparency. Even better, a shape can be given states.
For example, the shape over the bottom tier could have an Initial State of Normal, and the others could have their Initial State set to Disabled. When the user clicks the bottom shape, one trigger would show the layer, and another trigger could change the state of the next shape to Normal.
In other cases, you could give transparent shapes Visited states. That gives you an easy way to track whether the user has clicked them all, so you could use that info in trigger conditions. For example:
Also, if you want to show the user that they click an area already, insert a checkmark or some other appropriate symbol in the shape's Visited state.
Hi Judy
I have tried doing the above triggers however, the hotspots don't appear for me to change their state:
Can you please advise, thank you.
Kind regards
Margaret
I have no idea how the trigger shown in your picture is related to this issue, since it's dealing with the states of a picture and of an arrow based on the values in multiple variables.
You said, "the hotspots don't appear for me to change their state."
As noted above, hotspots don't have states. A shape with a solid fill set to 100% transparency would be invisible to the user (like a hotspot is), However, a shape can have states. (See PRIMER: Hotspots vs. Transparent Shapes | Articulate - Community )
Beyond that, troubleshooting is just guessing without seeing all the programming. Someone might be able to solve the issue if you upload the .story file. Here are the best practices for doing that:- Only include slides that are related to the problem.
- Be sure objects, layers, motion paths, and variables have meaningful names.
- If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.