- Geo slide: alphabetically clicks on countries (used English names, not the original names of the coutnries)
- Keypad slide typing the pincode on a numeric keypad.
First and last slide are taken from the Quick Start Project 'Aspire'. The images used as button also are from the Assets panel.
You probably will have more ideas where this workflow can be used for Knowledge Check slides. There is a sequence type of quiz slide, you can test a sequence with Drag&Drop slides, but these alternatives are less limited in design. ould love to hear your proposals for sequence checks as well
- v_counter: will track the number of clicks on interactive objects. It starts with a default value of 0. It is reused on the second sequence slide, by resetting to the default value using the On Enter action of that slide.
- v_correct: will track the number of correct clicks, set up with default value of 0 and re-used in the same way as the previous variable.
The Normal state is empty (easy to reset, will automatically reset when returning to the slide if ‘Retain State’ is unchecked). The 6 following states correspond with the correct sequence, hence their labeling. The last state is the Wrong state. The sequence of states is important, because I will be using the ‘Go to Next State’ command in the actions.
The group Gr_Wrong on the Keypad groups all button SVGS which are not used in the pincode. Those buttons are on top of the image, and can be hidden, since the remaining keypad image shows them as well but in a non-interactive version. For the Geo slide, the colored country SVG buttons are also on top of a big SVG (Europe), but I don’t want the colored ones to disappear, for that reason the buttons will be disabled, not hidden (see advanced actions below).
Actions and events – Geo slide
Only the items marked by a red oval have to be switched for the actions SV2….SV5Act: the name of the SVG button in the first decision, and the literal (number) in the second decision. If the clicked country is not fitting in the correct sequence, the learner sees the Wrong state in the multistate shape and the Retry button will appear.
The last country SVG button (SV6) has a slightly different action, derived from the previous one. Reason: the Next button has to appear if the sequence is correct. That extra command is highlighted by a blue rectangle.
The Next button has the default command ‘Go to Next Slide’ on its Success event.
The Retry button needs to everything, as you can see in this screenshot. Action is triggered by the Success event:
Actions and events – Keypad slide
Some explanation may be needed for the Hide command which I highlighted. Since the required pincode (29791) needs the number ‘9’ twice (second and fourth position in the sequence) I have put two SVGs on top of each other: SVG_Two and SVG_Four. By default SVG_Two is visible, but SVG_Four is hidden and becomes visible With the same action where SVG_Two is hidden. You cannot have two interactive objects on top of each other when both are active at the same location.
The Number buttons trigger an advanced action On Success. It is similar to the one in the Geo slide, except for using Hiding instead of disabling. Example of the first number button (which is 2):
As explained above, for SVG_Second (number 9) is bit different
Similar to the Geo slide, the last correct button (number 1) will show the Next button if all was correct:
Any wrong number button will trigger this action using its Success event:
The new Retry button, labeled RetryBis is similar to the one on the Geo slide, triggers:
Remember that the SVG button Four is in the same location as Two, because both have the number 9. That is why SVG_Four has to be hidden and SVG_Two shown.
Why no Shared Actions?
- The SVG button SV_1 – compulsory parameter in the first decision
- The literal ‘1’ in the condition of the second edition, not compulsory
- The multistate object Tx_Display, compulsory parameter in the second decision
- The state Wrong in the ELSE part of the second decision
- The button Bt_Next in the ELSE part of the second decision
Why is the literal a problem? Because it is also used in the Increment command. If you replace it by 2 for the second button, this will also be the case in the Increment command. I may have a workaround, but it is not always functional.
Second reason: with the workaround the parameters would increase to 6, which is my limit for a usable Shared action. Whereas using duplicate functionality for the advanced action is lot quicker, since only two items need to be edited.
This blog is already way too long. If you like to hear about my ‘thumb rules’ for choosing between duplicate advanced and shared actions, post a comment. Maybe I’ll dedicate another blog to it.