Multi-State Object Looping without advanced actions

[garyc56322630]

Hi,

Still lazy as always. 

I was pretty sure you could move from state to state using the the go the next state button.

I thought it was looping back to the normal state once the last step is reached.

I made it work few days ago and now it is not working... It is weird...

I do not want to create advanced action for this. 

Thoughts? 

Thanks

Gary

[Lilybiri]

Which version, please? I want to double-check although I have been using this quite a lot and it should loop back to first state.

[garyc56322630]

Hi,

It is 10.0.0.192 or either 9.0.0.437

Thanks,

Gary

[Lilybiri]

Tested on both, and after having seen the last added state, Go to Next state returned to the Normal state, real looping.

I cannot repro your problem. Which type of mult-state object?  I hope you are talking about custom states, because the commands Go to Next/Previous State do not work with InBuilt states.

[garyc56322630]

Hi,

It is shape used as button. I suppressed the inbuilt state and now it is working. I suspect that it was going to the inactive button state so was blocking any further interaction. 

This is my understanding. 

Thanks,

Gary

[Lilybiri]

That is not the case, I tried to explain: InBuilt states do not block anything, they just appear in specific situations. In case of the Shape button:

• Normal state: when user is not hovering over the button
• Rollover state: when user is hovering over the button
• Down state: when user is pressing the button
• Visited: after the user has pressed the button (if you are on CP2017, still ignore your version).

For those states it is NOT possible to use the commands Go to Next State, Go to Previous State.

Those commands only work on custom states. In case of shape buttons, if you have added two custom states 'One' and 'Two' those commands will cycle in a loop through the states: Normal, One, Two and then restart at Normal. The other InBuilt states will always keep their appearance.  Sorry to insist, but this is a public forum, don't want other users to be confused by your work flow where you claim that InBuilt states are blocking interactions, because that is not the case.

[garyc56322630]

Fair enough

In that case, could the button be inactive once I click on it and not then allow to move to other states? 

Can you send me your test so I understand the behavior please?

Thanks!

[Lilybiri]

There is some  misunderstading: inactive means to me that the button cannot be used to trigger an action. In that case you have to add the command Disable to the button action. It is not because the InBuilt states are taken out that the button is inactive.

I tend to make the Rollover and Down state 'neutral', so that it fits with all custom states that could replace the Normal state. Have a look at this article in which I created toggle buttons, where the Normal state is replaced by an alternative custom state when the status changes:

1 action = 5 Toggle Buttons - Captivate blog

If you do not want rollover and down states, you can delete them indeed.