One of the many new features in Captivate 9 is the ability to additional states to objects. Usually objects have three states, Up, Rollover and Down. You can now add custom states to objects and then use the Change State action in advanced actions to display object states as needed. Here is some info on multi-state objects.
After downloading CP9, I thought I’d explore this new feature first and figure out the workflow. It’s very easy to use; in an object’s Property Panel, there is now a State View button that opens up a filmstrip-like window.
In this panel, you can manage the states of an object, add/delete states, add other objects or bitmaps to a state, etc. It’s very intuitive; once you understand the concept of states, it’s a snap to set up and use in simple or advanced actions.
For my test project, I decided to work with an image set I had previously used to build a slider interaction in Articulate Storyline2.
I wanted to explore two options for state changes: The first option uses up/down buttons to increase/decrease the value of a variable. Based on a that value, a particular state of an image object is displayed.
The second option is a variation of the first on and, instead of clickable buttons, allows the mouse to be used for state changes.
This great new feature opens up lots of possibilities for interactive elements, e.g sliders. Well done Captivate! I will keep experimenting with multi-state objects and use them from now on in new projects.
Here is my first attempt to use custom states in CP9.
Hi Michael, I love your example! Can you pls explain the procedure you used for the second option where the closing of the doors is done by a slider!
The slider was done as described in this blog post here: http://wp.me/p2BoUf-dI
Thanks for your reaction Michael, just the screens on the page from the supported link look very different (like a single step action) and not very clear how that was done also. Already 3 requests for extra explanaition on that page also ;(
Pls some extra guidance.
Would you by chance know how to set conditional/standard actions to make a next button appear after a certain number of states were viewed from a multistate object?
That very much depends on your specific setup. Maybe you could use a variable that increases with each state and then enables the Next button.