Some of the simple tips offered during the presentation at Adobe eLearning Conference – Washington DC (25th of April 2018). No variables, no advanced actions, no shared actions are used in the post.
Last week at the Adobe eLearning Conference in DC I presented two sessions about the Timeline. The first part ‘Demystifying Captvate’s Timeline’ allowed me to explain the basics without having to rush as was the case in the Adobe Learning Summit at Las Vegas 2017 (watch the interactive version of that presentation in: Captivate’s Timeline). The second part ‘Mastering TImeline’ had its focus on more advanced workflows, using micronavigation, advanced/shared actions and multistate objects. In the first part I didn’t use any advanced nor shared action, just offered some small practical tips. For those who couldn’t participate in the conference I will summarize those tips.In this article you’ll find 3 tweaks.
Tip 1: Pausing all slides at the end
This request often appears in the forum, and is also useful when using Captivate for presentations (as I usually do). The user has to take an action to continue to the next slide. Two possible situations: you are using a default playbar, or custom navigation. Both workflows are using a shape button on master slides. Shape buttons are the only interactive objects allowed on master slides. You can use them in non-responsive and responsive projects (both Fluid boxes and Breakpoint views).
With Default Playbar
- Open the Master slide panel
- Select the Main Master slide
- Add a shape button, with Alpha = 0 for the Fill and width = 0 for the stroke to make it invisible to the user
- Check the settings for that shape button in the Actions tab of its Properties panel, to look like this screenshot:
No action is needed for this shape button, its unique use is to Pause the slide. Each shape button set up this way will pause slides using this master slide at the end of the slide, whatever its duration.
- Check if the daughter master slides have the option ‘Show Main Master Slide Objects’ checked. With the included themes, that is the case for most master slides, with the exception of the Title and the Blank master slide.
With Custom Navigation
If you use master slides with an inserted Back and/or Next shape button for custom navigation, you can use that shape button with the same settings as described under the previous workflow. Those buttons will have a Fill and perhaps also a stroke, and they may not be on the main master slide but on other master slides. You just have to check that each master slide has at least one shape button to pause the slide.
Tip 2: Reset a slide
This tweak can be used in several situations:
- to reset a knowledge check slide
- to reset a Drag&Drop slide configured as knowledge check slide
- to reset effects, including motion effects
In the second presentation I explained an advanced workflow using micronavigation, but this workflow is easier, though it will increase the number of slides, which means that you cannot use the system variables cpInfoCurrentSlide and cpInfoSlideCount to show the progess of the slides. Try this out:
- Insert a short dummy slide before the slide that you want to reset. Give it a timing of 0,1sec (shortest possible).
- On the slide to reset, insert a (shape) button which you can style as you wish.
- The success action of that button should be: Go to Previous Slide’. When you click that button, the playhead moves to the previous slide which is so short that it is practically invisible. Since the content slide is re-entered it will automatically be reset for the situations mentioned above.
This workflow is also valid for all types of cptx-projects, responsive or not.
Tip 3: Avoiding frustration in Quiz
Quiz and score slides have a default pausing point at 1.5secs. That pausing point is visible on the Timeline, but is not present in the Timing Properties panel. Here is a short description of the ‘role’ of this pausing point:
- On Quiz slides it is linked with the two-step Submit process (and Submit button). In the first step the playhead remains paused while the learner sees the feedback messages. In the second step, the playhead is released. If you keep the default Success/Last Attempt actions set to Continue, the playhead has to visit all the frames in the inactive part of the quiz slide (part after the pausing point) before reaching the next slide. You could change those actions to ‘Go to Next slide’, but sometimes (depending on the setup for transmitting the score, bandwidth etc) this could lead to problems.
- On the Score slide the pausing point is linked with the Continue button. Contrary to the Submit pausing, the actions triggered by that button which you specify in the Quiz Preferences (If passing/failing grade) are only done when the playhead reaches the last frame of the score slide.
In both cases you can avoid frustrations by dragging the pausing point closer to the end of the slide timeline, but not completely till the end (leave a small inactive part).
Moving the pausing point is even more required when you have slide audio on the question or score slide. In almost all cases, that slide audio will result in a longer slide duration than the default 3 seconds. You have to know that it is not possible to pause slide audio on a quiz/score slide by a pausing point, as is possible on other slides when using an interactive object. You may not be aware of the pause at all, audio will just continue. Many users are confused by that. If you leave the pausing point at 1,5secs, the learner will have to wait a frustrating long time when completing the Submit process (quiz slide) or leaving the score slide with the Continue button. Make sure to drag the pausing point in such a situation:
This workflow is valid for all types of projects, responsive and non-responsive.
Tip 4: Forcing views
As a professor with a lot of experience in tutorials for adult learners, I really dislike this request that appears too often on the forums: how can we force a learner to ‘view’ all the content on a slide. Forcing viewing doesn’t mean understanding, nor learning at all, can even have the opposite effect. But that is off topic.
You have to forget the default playbar in this situation. Each slide will need a Next button. The timeline of that button has to start after all content has appeared and all audio has been listened to. Timelne will look similar to this screenshot:
The workflow is valid for all types of projects. For Fluid Boxes you have to be careful not to stack objects.
Such a setup will become very annoying if you allow the user to revist the slide: he will have to wait again until all audio has played and all content has appeared to be able to proceed. Is there a solution? Sure, but not without advanced/shared actions. Watch out for a next blog post, linked with the second part of the Timeline presentation. I will offer you a shared action that makes it very easy to avoid that boring situation on second and later visits.