Skip to main content
Known Participant
November 25, 2015
Answered

Multi-state, smart object in cap 9

  • November 25, 2015
  • 2 replies
  • 286 views

I have 5 multi-state buttons on 1 slide. Each one changes the state of a separate object. This all works as intended with the exception that I would like each button to remand in a down state once clicked. Do I need to change each button's action to an advanced action that changes the state to the separate object AND change the state of the button itself to the down state to make this work? If so, what is the point of having a down state on a on a smart shape button if it doesn't stay in the down state once clicked?

Thanks in advance for any answers.

    This topic has been closed for replies.
    Correct answer Lilybiri

    Variables are so close to advanced/shared actions   How can you live without variables when telling you are experienced with advanced actions, I don't get it. The easiest way to start with advanced or shared actions is using the system variables in the group 'Movie Control'.

    What I explained about button states is common to all buttons in all applications, not only to shape buttons in Captivate. Just to clarify.  The limitation that exist in Captivate is that you cannot change the form for Inbuilt states (hope that changes later on), but you can add as many custom states as you want and those have no limitations. Create a 4th state that looks like your down state, which is very easy with shapes.

    2 replies

    Lilybiri
    Legend
    November 25, 2015

    A down state is normally meant to appear only when the button is 'down'. This may not be what you expected, but it is a 'normal' behavior.

    If you want to see a difference, you can add a custom state to the InBuilt states, that will replace the Normal state only (which is the state when the button is not rolled over nor clicked), the rollover and the down state will remain. I used this work flow for the toggle buttons in this blog post:

    1 action = 5 Toggle Buttons - Captivate blog

    You will see that I used the same shared action for different buttons. Maybe you could try that out?

    Known Participant
    November 25, 2015

    Thanks Lilybiri. Perhaps I misunderstand the purpose of the down state.  The buttons have the Normal or unclicked state, the RollOver which works when the cursor is placed over the button, and the down state, which I expected to be the state in which the button remains once clicked. Instead the button returns to the normal state once clicked and does not remain in the down state. If this is indeed how the multi state smart button works than I will try the solution you describe. I am experienced with advanced actions but I rarely use variables so I would prefer a work around without the variables. If you know of any other way I would appreciate the guidance.

    Lilybiri
    LilybiriCorrect answer
    Legend
    November 25, 2015

    Variables are so close to advanced/shared actions   How can you live without variables when telling you are experienced with advanced actions, I don't get it. The easiest way to start with advanced or shared actions is using the system variables in the group 'Movie Control'.

    What I explained about button states is common to all buttons in all applications, not only to shape buttons in Captivate. Just to clarify.  The limitation that exist in Captivate is that you cannot change the form for Inbuilt states (hope that changes later on), but you can add as many custom states as you want and those have no limitations. Create a 4th state that looks like your down state, which is very easy with shapes.

    Known Participant
    November 25, 2015

    Update. One cannot change the state of a smart shape used as a button. Thus I can't even use an advanced action to achieve my goal unless a create another smart object to look like the down state of the button and show that in the advanced action. Again, this seems to defeat the purpose of the down multi-state on a smart object button. Am I going about this all wrong? is there an easier way to do this?