I created a slide where the learner sees an interactive jigsaw puzzle. Each puzzle piece can be clicked on in any order for learner to be taken to a layer that provides more content on that puzzle piece. There is a trigger within each layer taking the learner back to the main jigsaw puzzle slide.
I want to create a trigger where the main jigsaw puzzle slide only advances to the next slide once the learner has jumped back to the main jigsaw puzzle slide after having viewed all of the layers. How do I do that? I assume I need to use variables, but I'm not quite sure how to set it up.
Hotspots come with a lot of built-in baggage. If you need it, it's wonderful, but I usually don't. I find more flexibility using shapes with no outline, and their transparency set to 99%. (In this case, I set the transparency a lot lower, so you can see the shapes.)
The same is true with the built-in NEXT button, lots of baggage, not enough flexibility.
Thank you for responding. I reviewed your document and I tried out these suggestions. It's still not working.
I have saved the slides in question as a file and am uploading them here. I deleted the audio and syncing to reduce the time in each layer. Please let me know if there's something I'm not doing right. Thank you for your help!
Two problems with these triggers , and the ones like them on the other layers:
The biggest problem is that once the jump to trigger is executed, all the rest of the triggers that fire when the user clicks Button 1 are ignored. So the variable is not changed, and the End layer trigger is not evaluated to see if it should be shown or not. This is a really valuable piece of information for every spot in a project, that once a jump to trigger is encountered, none of the triggers below it are executed.
In this particular case, I would not jump to this slide, I would just Hide this layer. Changing between layers and the base does not interrupt a chain of triggers. In this case, it would also allow you to create a visited state that could be applied to either the rectangles, or the underlying png. If you change the png, you would need a trigger to do that, and I would recommend a custom name for the state. Creating triggers to duplicated the built-in functions can cause conflicts.
Another thought is that you could get by without the End Layer, unless you have additional information to present there. Instead of showing that layer, the other layers can jump to the next slide if all the variables are true, or they can hide themselves and show the NEXT button.
I roughly applied a couple of those ideas to the two lower puzzle pieces, so you can see them in action.
5 Replies
Here's a sample that can help you get started.
Some things to note:
Hotspots come with a lot of built-in baggage. If you need it, it's wonderful, but I usually don't. I find more flexibility using shapes with no outline, and their transparency set to 99%. (In this case, I set the transparency a lot lower, so you can see the shapes.)
The same is true with the built-in NEXT button, lots of baggage, not enough flexibility.
Hi Walt,
Thank you for responding. I reviewed your document and I tried out these suggestions. It's still not working.
I have saved the slides in question as a file and am uploading them here. I deleted the audio and syncing to reduce the time in each layer. Please let me know if there's something I'm not doing right. Thank you for your help!
Two problems with these triggers , and the ones like them on the other layers:
The biggest problem is that once the jump to trigger is executed, all the rest of the triggers that fire when the user clicks Button 1 are ignored. So the variable is not changed, and the End layer trigger is not evaluated to see if it should be shown or not. This is a really valuable piece of information for every spot in a project, that once a jump to trigger is encountered, none of the triggers below it are executed.
In this particular case, I would not jump to this slide, I would just Hide this layer. Changing between layers and the base does not interrupt a chain of triggers. In this case, it would also allow you to create a visited state that could be applied to either the rectangles, or the underlying png. If you change the png, you would need a trigger to do that, and I would recommend a custom name for the state. Creating triggers to duplicated the built-in functions can cause conflicts.
Another thought is that you could get by without the End Layer, unless you have additional information to present there. Instead of showing that layer, the other layers can jump to the next slide if all the variables are true, or they can hide themselves and show the NEXT button.
I roughly applied a couple of those ideas to the two lower puzzle pieces, so you can see them in action.
Thank you Walt. I am trying this out now. I tested it and it works! I hid the layer instead of jumping to the same slide.
I also had to add "set variable x to true if user clicks button". Without that, it doesn't work.
Thanks so much!
You're welcome. PIAWYC (Pass it along when you can).