This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Have you noticed that when you save a custom image to a macro it multiplies the file size? Below I will outline why I believe this happens and how it could potentially be fixed.
When a image is saved in the XML of a macro, it is saved in a single line of XML code that is generally quite long. I believe the problem this causes is that this very long image code extends the length of all other lines to this new max length. This increased line length seems to increase the file size and is multiplicative based on how many lines of XML that have been extended in the macro. For example, I added a 5KB image to a 7KB macro and saving the macro resulted in a 29KB file size. I have also experienced saving a 5KB image to a 300KB macro that yielded a 1.4MB macro.
In the (very zoomed out) image below, you can see the single line that contains the image information for this simple macro.
Images are saved in the Image tool by splitting the image information into multiple lines. I suggest this same methodology be introduced to custom images loaded to macros. The image below shows the XML of the Image tool that has the same image as the macro stored.
I mentioned this in the Solutions Center at Inspire 2016, but I wanted to follow up here to make sure it wasn't lost in the mix.