Skip to main content
Inspiring
January 29, 2024
Question

Captivate Classic Disabling progress bar via JavaScript

  • January 29, 2024
  • 1 reply
  • 335 views

I have a block of Javascript code that I have included on slideEnter on the first slide of my Captivate Classsic project.

It works exactly as it should and disables the progress bar (making it read only). 

I am not sure it will also work if the user returns to the course mid-way though (via a bookmark from the LMS for example)

Does anyway have experience running Javascript form the first slide like this?

    This topic has been closed for replies.

    1 reply

    Inspiring
    January 29, 2024

    It doesnt work with boomarking unfortunately

     

    Lilybiri
    Legend
    January 30, 2024

    I am a bit confused now. You talk about bookmarks. In Captivate Classic those bookmarks are only available on slides with slide video. Are you sure about the version you are using? Bookmarks are available on all content slides, excluding the question slides in the New version of Captivate. But you may refer to the term 'bookmarking' as it is used in connection with the LMS Resume Data? Since JS is executed on runtime, if it is on the first slide when resuming another session it will not be activated.

    I suppose you want to keep the progress bar to show the progress, but prevent the scrubbing. This is a long-time standing feature request. I have explained some workarounds in blog posts for Captivate Classic to show the progress (without a bar) which will also be functional in a non-linear project. That makes it less confusing because the default progress bar is only valid in a pure linear project:

    https://blog.lilybiri.com/percentage-progress-indicator-non-linear-course-solution-1

    https://blog.lilybiri.com/percentage-progress-indicator-non-linear-course-solution-2

     

     

    Inspiring
    January 30, 2024

    I am referring to bookmarking as in "return the user to where they were when revisiting the course"

    I can add my code directly to the published html file but it is ridiculous that I have to do that. It seems like  Adobe just ignores basic functionality requests in favor of implementing whatever is the latest buzzword.