Why you should use “cloned” images

Helpinator’s “Image Library” allows you to create “cloned” images. What are they?


Let’s say you have a big complicated tool bar in your application. You need to explain your users how to work with it, what buttons trigger specific actions, all grouped by specific tasks… This probably will require a lot of copies of the toolbar image, each one with it’s own callouts, arrows and text boxes, but all with the same background – application toolbar.


Now suppose that during project evolution toolbar changes significantly – updated icons, some new buttons. Now you need to update a bunch of images to reflect changes in the UI. That could be a nightmare! But not if you use Helpinator’s image library and “cloned” images.


In the following example will’ take a look at one simple but very common situation. Suppose you have a set of images in your project, describing different parts of the toolbar, but all of them contain application name and version in the  window title like this:




One image has callouts for language bar:




Another for compile buttons, and so on…




We’ll make the first one “donor” image and two other images will be cloned.




Now suppose application version changes to 3.5. You need to update all those images. Luckily you have only one basic image and two clones, so you only need to update one image.


Select Tools->Replace bitmap when basic image is open in the editor.




Now all cloned images are updated: