Update
If you are using CP2019, version 11.5 where you can use SVGs as buttons, with possible limitation of the clickable area to the image itself instead of the bounding box, have a look at this updated version of a custom hotspot question:
Intro
Why?
- hotspots are always rectangular
- it is not possible to have partial scoring
- you cannot add shape buttons to that type of slide, because any space outside of the correct hotspots causes failure
- freeform hotspots
- partial scoring, that can be reported to a LMS by SCORM
- allowing to add shape buttons for more functionality
Why not?
- custom question slides always take more time (although shared actions can help), especially if you want to add all question functionality (Clear, Retake etc...)
- if you like the animations that appear on clicked hotspots, they are not added automatically in custom hotspots, there is of course a way of showing the clicked hotspots
- although the total score will be correct when using partial scoring, some quizzing system vars will consider each correct hotspot as being a separate question; you have to be careful when using a default score slide, in which you show number of questions/correct questions
- it is not possible to use custom questions in a question pool
Example
Concept Hotspot Question - version 1
- v_attempt: number allowed attempts; will be reused for second question, number is assigned by On Enter action
- v_counter: counts the clicks, to be compared with v_attempt; will be reused for second question, reset to 0 by On Enter action
- v_wrong: counts the mistakes, is not reset because it will continue to increment on second question, is used on custom score slide.
- "Always" is a mimicked standard action, self-explanatory. Because this hotspot can be clicked multiple times, the last statement is necessary to place the playhead one frame back, in the active portion of the shape button.
- "ShowNext" checks if the number of allowed attempts is reached, and if that is the case will hide all the hotspots and shows the Next button.
For the correct hotspots, that allow only one click, I created a shared action with two decisions
- "Always" is a mimicked standard action, self-explanatory. The parameters are highlighted.
- "Checker" is similar to the second decision for the incorrect hotspot. Parameters are highlighted.
The On Enter action for this slide is a standard shared action that resets the value of v_counter and v_wrong to 0 and assigns a value to v_attempt.
Concept Hotspot Question - version 2