Skip to main content
Participating Frequently
December 14, 2016
Answered

Making objects into buttons within State View with Captivate 9

  • December 14, 2016
  • 1 reply
  • 648 views

My apologies if this has been answered before.

I'd like for the learner to only be able to move forward from a slide after they have clicked a button I created that displays useful information within the state view, or next state, for that object. Is it possible, or what is the best way, to create a "next" button within that object's state view to ensure they can only move forward once they have clicked that object and read the information?

Happy to provide additional information into the situation I'm trying to create.

Thanks in advance for your help!

This topic has been closed for replies.
Correct answer Lilybiri

A (shape) button has only one Success event, that can trigger an advanced action. If I understand your requirement correctly, it is a bit confusing, you want that button to display first more information, then to click again to go to the next slide. BTW although you can force that information to appear, you never can force a human to read it

Just with states that will not be possible, since you need two actions, you'll need two interactive objects. This could be a workflow:

  • Create two identical (shape) buttons and check the style of the InBuilt States; I will label those buttons SB_One and SB_Two
  • Put them in exactly the same location (use Align option)
  • Make the second button invisible in output (eye icon on the Properties panel)
  • For SB_One, add a custom state 'Info' that shows the wanted information
  • For SB_One create this advanced (or shared) action:
    • Change state of SB_One to 'Info'
    • Disable SB_One
    • Delay Next actions by x seconds                  x needs to be the estimated time needed to read the info
    • Hide SB_One
    • Show SB_Two
    • Enable SB_Two
  • For SB_Two the simple action 'Go to Next Slide' is OK.

Beware: this is a case where replacing the custom state by a text container with the info (or a group if you need more than just text) would perhaps be a better choice. That container (or group) should be invisible in output. The action for SB_One would be in that case:

  • Show Text (or group)
  • Disable SB_One
  • Hide SB_One
  • Show SB_Two
  • Enable SB_Two

1 reply

Lilybiri
LilybiriCorrect answer
Legend
December 14, 2016

A (shape) button has only one Success event, that can trigger an advanced action. If I understand your requirement correctly, it is a bit confusing, you want that button to display first more information, then to click again to go to the next slide. BTW although you can force that information to appear, you never can force a human to read it

Just with states that will not be possible, since you need two actions, you'll need two interactive objects. This could be a workflow:

  • Create two identical (shape) buttons and check the style of the InBuilt States; I will label those buttons SB_One and SB_Two
  • Put them in exactly the same location (use Align option)
  • Make the second button invisible in output (eye icon on the Properties panel)
  • For SB_One, add a custom state 'Info' that shows the wanted information
  • For SB_One create this advanced (or shared) action:
    • Change state of SB_One to 'Info'
    • Disable SB_One
    • Delay Next actions by x seconds                  x needs to be the estimated time needed to read the info
    • Hide SB_One
    • Show SB_Two
    • Enable SB_Two
  • For SB_Two the simple action 'Go to Next Slide' is OK.

Beware: this is a case where replacing the custom state by a text container with the info (or a group if you need more than just text) would perhaps be a better choice. That container (or group) should be invisible in output. The action for SB_One would be in that case:

  • Show Text (or group)
  • Disable SB_One
  • Hide SB_One
  • Show SB_Two
  • Enable SB_Two
rickpechAuthor
Participating Frequently
December 15, 2016

Thanks Lily for again taking the time to respond to my question. I appreciate it the help as I get to know some of the nuances of the program.