Can we change the state of an image used as a button with a variable in advanced actions?

Question

With the update to Captivate 2019 released this last year, we can now use an image as a button and set up states for that image button. However, when trying to set up advanced actions for clicking image buttons to reveal text on the slide, Captivate does not appear to allow us to change the state of the image when I set up a conditional statement with a variable to show the image in the visited state once it has been clicked on the slide. Has anyone else run into this and found a solution?

I'm disappointed if we can now use images as buttons but cannot change their state within an advanced action.

RodWard · Accepted Answer

I haven't seen this issue. I am able to add an image to a slide, configure it as a button, add the Visited state, and set another button on the same slide to change the image button state to visited.

Could you please try setting up a single slide test project as I have described above? If you are able to make an image button turn to visited state using another button as a test, then it may be that the real issue is a logic flaw in your Conditional Advanced Action.

Lilybiri · Answer

The Visited state is an InBuilt state, which should appear once the button has been clicked. Is there any reason why you used an InBuilt state which occurs in a certain situation over a custom state? However it is perfectly possible to use that InBuilt state in a conditional action (which is not the case for all InBuilt states).

I am a bit confused by the title of this thread: can you post the advanced action you are using? I wonder about the functionality of the variable you talk about?

Both bitmap images and SVGs used as buttons have one big drawback: you cannot create an object style for them. That is the reason why I still prefer shape buttons filled with an image over bitmap images used as buttons. However I do use SVGs as buttons when possible (although there is a small lag on loading) because you can restrict the clickable area to the button instead of the bounding box.

Maybe you could find some more details in:

http://blog.lilybiri.com/overvew-6-button-types

http://blog.lilybiri.com/about-state-commands-and-a-progress-bar