Replace Image in Image Button

Forum|Forum|6 years ago
August 13, 2019
1 reply
1233 views

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.

This topic has been closed for replies.

Correct answer Lilybiri

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:

Button Types

LilybiriCorrect answer

Legend

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:

Button Types

D

Dave_BSMAuthor

Participating Frequently

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.

Lilybiri

Legend

Sorry to disagree completely, and I will try to explain by comparing Image buttons with shape buttons:

Creation: for Image buttons you need a graphics application, where you create 3 images of same size, which need to have identical names except for _up, _over, _down. Lengthy process, cannot be done in Captivate.
Shape buttons can be created in Cp: import the images to the Library and use them to fill the shape.
Only drawback: snce 'fit shape to image' is lacking you have to be careful with the shape size.Label: no label is possible in an Image button it needs to be part of the image.
For shape button: double click the shape and add a label with full formatting possible.
Use: Image button can not be used on master slides, cannot be timed for the rest of the project. It cannot be added as extra button the quiz/score slides, can be used as embedded button type for those slides.
Shape button can be used on Master slides, can be timed for the rest of the project, can be used as extra button on quiz/score slides. Cannot be used as embedded buttons (but transparent button can have exactly same look/style)
Style: image buttons will automatically be added to the style list, making it difficult to manage with the amount of image buttons you mention.
For Shape buttons you can choose to create an object style, which makes sense for frequently used buttons in projects, since object styles are part of the theme, core of consistent design. For less frequent used buttons, you do not need to create an object style at all. That makes the list much more easy to manage.
Editing: is a pain in .... for image buttons, if you want to edit the image or replace it. For shape buttons it is a breeze: used images for states are in the Library and you can edit them like you do for any Library asset. Replacing is just pointing to another image, editing can be done in a limited way with Edit Image, or by roundtripping to PS (or AI). Both are impossible for image buttons.

Finally my recommendation:

Shape uttons for those you want to use over and over again, with creation of an object style saved in the comoany theme.
BItmaps or SVG (my preference) for less frequent used buttons, which are project only. Have a look at my recent blog/
SVG's for Custom Hotspot Question - Captivate blog
No styles needed here, will not reuse thos SVG' buttons. They have a big advantage over shape buttons and image buttons: you can control the clickable area.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.