Skip to main content
Known Participant
January 9, 2018
Answered

Advanced Action not working when alt-tabbed

  • January 9, 2018
  • 2 replies
  • 432 views

Hello everyone!

I encountered a bug in Adobe Captivate and I wanted to know what are the workarounds for it.

In my current project. people have to press the Continue button to go from slide to slide. In some slides, I change the timing of the "Continue" button to appear after a few seconds, usually in situation where I suspect some users will repeatedly hit continue without checking the content.

I did this by using the "Appear after XX seconds" option in Timing.

The problem I encounter is that, if I am alt-tabbed, the Continue button just doesn't appear at all, at least in Google Chrome for Windows. I got the same result from Preview and from the version in my LMS.

Is this a known issue?

I stopped using that function and instead relied on an Advanced Action that hides/shows the button (which works while Alt-tabbed), but I was wondering if I should avoid Timing events altogether based on this experience, or if there is a rapid fix I could use to avoid changing all other slides where I have programmed the same basic concept?

Thank you all once again for your help.

Enjoy 2018!

    This topic has been closed for replies.
    Correct answer Lilybiri

    Understand now what you meant, sorry, I'm not a native English speaker. I will try to explore. My statement that the While and Delay commands will continue whatever happens, is confirmed. In this case opening another browser window. I wonder why the the timeline seems to be stopped? May I ask you for a test? Can you insert the system variable cpInfoCurrentFrame on such a slide (or in the project, timed for the rest of the project, always on top)? Can you check if the frame number has increased when you come back to the course window?

    2 replies

    Lilybiri
    Legend
    January 11, 2018

    I understand that this is working when you use the Delay command in an advanced action with Show/Hide and have the button on the timeline from the start, but not when you use the timeline to let the button appear later. The Delay command is never bothered by any pausing point on the timeline (same as the While loop). However the appearance of the button will not happen if there is a pausing before the start of its timeline. What do you mean exactly by alt-tabbing?

    GamashireAuthor
    Known Participant
    January 11, 2018

    When I use the Timeline to make the button appear after 10 seconds:

    • If the training module remains my active window in Google Chrome, everything works properly.
    • However, if, after entering the slide, I go to another tab in Google Chrome, wait for 20 seconds, and come back to my e-learning module, the button will never appear at all.

    Of course, users are not supposed to change tabs when following training, but it's a bit naive to think that no user will ever do it. And if my NEXT button never appears, the user is stuck in that slide forever unless the page is reloaded to start again from scratch.

    Lilybiri
    LilybiriCorrect answer
    Legend
    January 11, 2018

    Understand now what you meant, sorry, I'm not a native English speaker. I will try to explore. My statement that the While and Delay commands will continue whatever happens, is confirmed. In this case opening another browser window. I wonder why the the timeline seems to be stopped? May I ask you for a test? Can you insert the system variable cpInfoCurrentFrame on such a slide (or in the project, timed for the rest of the project, always on top)? Can you check if the frame number has increased when you come back to the course window?

    Paul Wilson CTDP
    Community Expert
    Community Expert
    January 10, 2018

    Have you tried simply delaying the objects appearance on the timeline instead of using advanced actions? I'm away from my computer so I'm not sure if it will make a difference but worth a try.

    Paul Wilson, CTDP
    GamashireAuthor
    Known Participant
    January 10, 2018

    The issue occured when I used the timeline.

    It works fine in Advanced Actions.