Skip to main content
jumper5558
Known Participant
July 11, 2018
Question

Captivate 9: Limit users from pressing buttons for a few seconds

  • July 11, 2018
  • 1 reply
  • 2258 views

Hello,

I am making a training module and I have a few slides where I put "Click to Reveal" animations. I did this by creating states with audio and when a user presses on a button it will open the corresponding state using an advanced option. If the user clicks on all buttons, the continue to next slide button becomes active.

How do I limit the user from just pressing on all the buttons on the slide to just advance to next slide? Some of these have really important audio that there is just no room to place on the slide.

Please post any solutions you may have or ask any questions you have that need to be clarified.


Thank you so much!

This topic has been closed for replies.

1 reply

Lilybiri
Legend
July 11, 2018

Use a shared action, disable the other buttons for as long as the audio has to play, by using the Delay command. After that delay you enable them again. Typical use case for shared actions....

jumper5558
Known Participant
July 13, 2018

Hi, so I did the disable, delay enable for all buttons. Now the button I did it for isn't opening at all. The always do tab changes the state. The show next tab shows the continue button if all buttons on slide were shown. Please take a look at how I did disable, delay, enable and let me know if I did it wrong!

Thanks.

Inspiring
July 13, 2018

Which button triggers this action - button_49? Is this button visible at all on the stage or just not doing anything when clicked? If the latter, make sure that the correct advanced action is selected in the Script field of Properties -> Actions

Also, I normally disable the button that was clicked as well so that users can't repeatedly click and launch the same action when they're not supposed to. The other thing I normally do is have a "disabled" (grayed out) state for disabled buttons. This means more lines in the action to change all the states for all the disabled/enabled buttons - up to you.

To answer your question about the action setup - yes, it looks OK to me.