Skip to main content
ffami
ffami
Known Participant
April 19, 2017
Question

CP2017 - changing cpCmndCC with custom buttons not working

  • April 19, 2017
  • 4 replies
  • 2455 views

Hi!

I just switched my current project over to CP2017 and ran into this problem:

I'm using custom buttons to change the "cpCmndCC" variable to enable or disable closed captions.

However in the current version, this does not work.

It is possible to enable CC while audio with captions is playing, after it finishes, the variable gets changed back to 0 automatically.

If no audio is playing the variable is changed back to 0 immediately after clicking my custom button. So it's not possible to leave CC turned on.

I disabled the player skin for my project and if i turn it back on my buttons start working fine! Please help me fix this

This topic has been closed for replies.

4 replies

A
aamon1906
Participant
March 13, 2018

Here's the workaround I use in Captivate 2017:

1. In Skin Editor,

  • Check the Show Playback Control box at the top. Leave it on.
  • Check the Closed Captioning box at the bottom. Leave it on.
    • OPTIONAL: The Closed Captioning Settings button is where you can make sure your CC placement and size are correct for the entire project. *NOTE: While in this settings pane, if you check the Show CC box, closed captioning will be toggled ON by default when your project plays.

2. Back in your project, on slide 1 - Properties > Actions tab > On Enter: dropdown >Select Hide Playbar.

This will hide the default playbar throughout your project and allow your custom playbar/buttons to function like they should, toggling the CC window on & off. AND, the CC window will stop turning off completely on every new slide or every CC marker when synced with audio. The CC window will disappear when the audio ends on each slide. But, it will remain toggled on when the next slide's audio begins.

B
BP72
Known Participant
January 15, 2018

Was there a solution on this?

I am having the same problem with CC disabling each time a new slide loads.

Lilybiri
Lilybiri
Legend
January 15, 2018

With a custom button? There is a hotfix.

    B
    BP72
    Known Participant
    January 15, 2018

    It is with a custom button..

    Where might I be able to find this hotfix?

    Thank you

    zeeshan hussain
    Adobe Employee
    zeeshan hussain
    Adobe Employee
    April 19, 2017

    Issue exists in Captivate 2017. We are aware of this and are working on it. You will get an update soon.

    A simple workaround could be enable the playbar but hide it using on enter action on first slide using "cpCmndShowPlaybar".

    Regards,
    Zeeshan

    ffami
    ffamiAuthor
    Known Participant
    April 19, 2017

    Thanks to both of you, this will work for now

    But I'm still looking forward to the next update

    Lilybiri
    Lilybiri
    Legend
    April 19, 2017

    Will double-check, I'm busy doing that for most of my blog post examples, but didn't reach this one yet:

    1 action = 5 Toggle Buttons - Captivate blog

    Just a little bit of patience, please.

    Lilybiri
    Lilybiri
    Legend
    April 19, 2017

    It works fine for me, tested with Preview HTML5 in Browser (F11), and used Chrome as Browser. I didn't test for Flash output, and it was a normal, not a responsive project. Let me know if you want me to test more. I used a project created in CP9 and upgraded to 2017.

    I used the shared action with the states, described in that article for which I posted the link in my first answer.

    The captions disappear on the slide when the audio is finished, but the CC remains enabled, they appear immediately on the following slides when audio starts. This means that the system variable cpCmndCC is keeping its value.

    Which action did you use? Maybe you can explain your work flow.

    ffami
    ffamiAuthor
    Known Participant
    April 19, 2017

    Thank you for looking into it!

    I tested in Safari and FireFox in HTML5 and used an advanced action.

    I'm using a SmartShape which is visible for the whole project.

    It only does work for me if the player skin is activated.

    My action pretty much as simple as possible. I tried assigning 1 or 0 and toggling the variable, I attached an screenshot in this post.

    So I guess porting my project over from 9 to 2017 could have caused this problem ... I'm going to try this now in an empty project.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices