Here’s a quick tip:
And a common place for that function to be invoked was ‘On Exit’ (of the slide), so just as a given slide reached the end and ‘exited’ – about to move to the next slide – calling that custom action would pause the slide before playback brought the next slide onto the stage.
- You have to place the clickbox on every single slide. Even with copy/paste, you’ll likely have to adjust where the clickbox lies on the timeline.
- If the user doesn’t ‘click the box’ and uses some other method to advance to the next slide (i.e. Next in the playback bar), then the end of that slide is never reached, which will result in that slide not being ‘complete’…which can then be reflected in both TOC checkmarks and the SCORM-based completion status.
Fortunately there’s a better workaround! If you have an existing project with an Advanced Action intended to pause slides ‘On Exit’ then you can simply add another line with “Expression cpCmndGotoFrame = cpInfoCurrentFrame -1”. This tells the slide to jump back one frame, which avoids the incorrect (we assume) behavior where CP6 actually moves to the next frame before executing the actions specified in the ‘On Exit’ property. Here’s how we modified an earlier project that was upgraded to CP6 that contained this ‘PauseMe’ functionality: