This frustratingly gets even more broken when using images as image buttons.
I had to make a change to a few images that are used as 'Image Button'.
Update the image in library had NO EFFECT on the image in the button - captivate does not recognise an Image Button as an image - so it looks like each one has to be individually saved as a different name (because using the same name has no effect), brought into the library and then added as the image for the button. This is beyond frustrating.
If I am wrong and there is an easy solution for this problem, I would love to hear it.
I branched your question to an individual thread, because this is totally different from the one you added it to which was about replacing images, but not in an image button.
Since Captivate 6 I never used imae buttons anymore because of the very cumbersome workflow to create them and the issue you are mentinoing here. Replace them by a shape filled with an image (where you can easily replace the image in each state from within Captivate) or if you are using the most recent release, use the image itself as button.
Image buttons have no link whatsoever with items in the Library.... either you didn't explain clearly or the term 'image button' is wrong. Have a look at this overview of the button types:
Thank you. I think your solution of creating shapes, using as button and then fill as image is the best way.
I still think that this a fairly lengthy process (especially as the state for each button has to be changed) and seems to be work around for something that should work better - Image Buttons.
My main frustration was that I had spent so long creating over 20 individual Image Buttons for a project only to realise that there is no easy way to update the image in the button, hence having to almost start again.
Thanks for your help.
Sorry to disagree completely, and I will try to explain by comparing Image buttons with shape buttons:
Finally my recommendation:
Thanks Lilybiri for your detailed response, I hope this helps many other people as well.
You are 100% correct that shape buttons are the best way and I will surely never use Image Buttons again.
Not sure what you're completely disagreeing to as I agreed that your process is the best way, so thanks
I disagreed because of this sentence
"... seems to be work around for something that should work better - Image Buttons."
I don't like 'work around' which is to me deprecating the value of the most innovative feature ever introduced in CP, shape buttons. If only it would be possible to have the 'fit to shape' working as it should, this is still the best type of button.
Maybe I should put that comparison which I wrote in a short blog post...
Ahhh, makes sense I guess the reason I initially saw it as a workaround is due to the most obvious and intuitive way to create a button with an image (without captivate training) would be to go Interactions --> Button --> Image button
I agree, shape buttons are amazing but having to read blog posts, go to training courses or attend webinars to find out that they are best method to use an image as a button is still a flaw with the intuitiveness of the application.
As a result of your assistance and this exchange I now follow your blog, which is great, thank you. Hopefully I will avoid more frustration in the future.
I think putting this in a short blog post would be a great idea as I am sure it will help many others
May I answer with questions?
What would you think about giving a driver license to someone without any training? Could work if there were never other drivers on the road. That is why you can start a simple application as Word without any training. But what about allowing someone to fly an airplane without any training? That is what happens when you use Captivate without training.