HTML5 only issue: Playhead won’t move beyond Click Box Pause Point if Final Attempt reached prior to Pause Point

December 6, 2018
Former teacher turned professional eLearning designer/developer
Explorer 3 posts
Followers: 0 people
Sr. Learning Designer
9

HTML5 only issue: Playhead won’t move beyond Click Box Pause Point if Final Attempt reached prior to Pause Point

Former teacher turned professional eLearning designer/developer
Explorer 3 posts
Followers: 0 people
December 6, 2018

Hi.

Hoping someone can shed some light on this issue. We are using CP9, updated to most recent version, trying to publish software simulations in HTML5 output only. These are simulations for clients to complete on desktop devices, not mobile.

Below is the typical setup:

Using screen captures as backgrounds, we use the following objects on most slides.

  1. Single Click Box over the correct click location. Set to Go to the Next Slide on success, 3 attempts allowed, Continue on Final Attempt. Click Boxes are not included in quiz reporting for most slides.
  2. Just after the click box on the Timeline, we have a Smart Shape used as a button, which we use as a “step failure modal” – so if the user does not make the correct click in 3 tries the fail modal is displayed. User clicks the popup (fail modal) > slide continues forward > then we show mouse movement of the correct action. Project moves to the next slide. Object arrangement can be seen below:

Issue: This has always worked for us as we’ve traditionally published as SWF output. As we’ve tried to move to HTML5 only, we have found that if the use reaches the final attempt prior to the Pause Point set by the click box, the slide will hang at that point instead of moving beyond it to the step failure modal. If we wait until the slide reaches the Pause Point of the click box, and then make the final click, the slide will advance correctly. I should note our standard process is to provide text-to-speech at the slide audio level, which is why we extend the click box out so far. In some slides, this may extend out 20 seconds or more before the pause point.

**Question: Does anyone know why this happens in HTML5 only? Any input is helpful.

One workaround I’ve found is, we can add the audio directly to the click box. This enables us to shorten the click box to something like 2 or 3 seconds, which means the user is unlikely to use up all their attempts in this amount of time. But, to do this we must first generate the text-to-speech audio clip and then attach it to the click box. Editing the audio then also becomes an issue. This works for our purposes, but is not ideal, so I’m wondering if anyone has a better suggestion. I’m happy to share more detail, if it helps.

Thanks!

Brandon

Comments (9)
2018-12-10 19:47:22
2018-12-10 19:47:22

OK. Thanks, Lieve, for the links. I’ve read each of these before, and they are great resources. I don’t know if (for our purposes) it solves the issue. It does provide alternatives. I love the idea of micro-navigation using frames, but I’m not sure we can implement this at this time. We have a team of many learning designers who share these “standard objects” (as I’ve laid out in the example), so it may be difficult to quickly ramp up the whole team on this idea of using frames. Our design is to show the user a pop-up/modal when they have used up their attempts, before showing them the correct (mouse) movement. Not that your suggestion is incorrect, we’d just have to change our design.

I was hoping there was an easy explanation about why the playhead stops in HTML5 and not the SWF output (when user uses final attempt before the pause point of the click box), but I think HTML5 is just sensitive, as you said. We’ll keep looking into alternative ways to program this interaction. Right now, I like the option of adding the audio to the click box object itself. I’m also going to try this interaction in Cp2019 to see if it behaves the same way. I will report back when we land on a specific solution.

Thanks again.

Brandon

Like
(3)
>
brandons98972150
's comment
2018-12-10 19:50:55
2018-12-10 19:50:55
>
brandons98972150
's comment

No automatic mail sent anymore since quite a while. I check several times a day in the portal itself.

I don’t really expect changes in CP2019 concerning this sensitivity of HTML5 output, and cannot explain it. My answers were just based on my experiences, and I had quite a lot of use cases which didn’t work as expected when output is no longer SWF. Very frustrating.

Like
>
Lieve Weymeis
's comment
2018-12-10 23:22:27
2018-12-10 23:22:27
>
Lieve Weymeis
's comment

On the bright side, it’s how we learn many tricks and workarounds, right?

Thanks again for your insights and suggestions.

Like
>
brandons98972150
's comment
2018-12-11 09:29:15
2018-12-11 09:29:15
>
brandons98972150
's comment

Great, like that attitude! I learned Captivate almost exclusively by trying to solve problems for other users, and finding workarounds.

Like
(1)
2018-12-10 18:56:11
2018-12-10 18:56:11

Hi Lieve! Thanks for the reply. Sorry, I was looking for an email or some kind of notification that someone answered this. Didn’t see you replied until now. I will look into what you’ve said, and I will report back on any findings. Thanks so much!

Like
2018-12-09 11:31:41
2018-12-09 11:31:41

Can you please post a feedback: could you solve the problem with the provided information or not? I am asking this also for the sake of other users looking for answers to similar questions.

Like
2018-12-06 09:10:39
2018-12-06 09:10:39

Please look for my blog posts about the Timeline: especially the ones about Pausing the Timeline and Timeline and Audio clips.

Same for micro-navigation.

Like
2018-12-06 08:58:32
2018-12-06 08:58:32

Posted an answer to my question but it will take a while because of the links I included. I talked about slide audio not being paused by a pausing point (which would allow to shorten the slide duration). And my suggestion was to use micro-navigation to jump immediately to the mous object when necessary. Take out the second interactive object.

HTML output is lot more sensitive to  everything than the forgiving HTML output. The inactive part of an interactive object stays active as well.

Like
2018-12-06 08:56:23
2018-12-06 08:56:23

HTML5 output is much more sensitive to everything, also to advanced actions. You explained why that timeline is so long, because of the slide audio. However slide audio can continue beyond the pausing point, at least you could shorten the total slide duration. You can pause slide audio with a pausing point but it is not the case in the default setup. Maybe you could learn something from:

https://elearning.adobe.com/2017/02/pause-captivates-timeline/

https://elearning.adobe.com/2018/06/pausing-timeline-audio-clips/

Personally I would use micro-navigation to have the playhead jump immediately to the start of the mouse object if that is necessary, not use a second interactive object at all.

For micro-navigation you can visit:

https://elearning.adobe.com/2018/05/slides-frames-intro-micro-navigation/

Like
Add your comment