Use source image size on unscaled objects after exchanging the source image.

Nobody has claimed this yet.

(Thats an issue we already discussed in Discord a few weeks or months ago, but I forgot to open an issue as suggested. So I catch up on it now.)

Right now, if you place (image-) objects on a map the absolute size of the objects gets stored for each individual instance of the object. If you exchange the source image with a new one. All the placed objects will keep their old absolute size. So if the new image source is wider or higher all the objects will appear stretched or compressed.

Example: I have a map with a lot of decorative flowers and some bigger trees (alignment bottom-center). After I replaced the source images of the flowers and trees with new more beautiful ones that have a slightly different image size all the flowers and trees will appear stretched or compressed on the existing maps.

My suggestion for a (long-term solution) was to use scale variables instead of absolutes sizes, so a scale of 1 keeps always the original image size and a scale of 2 will always double it (keeping the integer scaling for pixel art games) even after changing the source image or its canvas sizes. But I understand that it might be a too fundamental change to the object properties.

**The solution @bjorn suggested instead was to not store the width and height values if the object has not been resized which would solve the problem for unscaled objects at least.**

Start by tracing how image-object width and height are stored and how objects respond when their source image is exchanged. Check the existing object-property and image-source handling before changing behavior. Done means unscaled objects use the replacement image's source size, while explicitly resized objects retain their dimensions; the issue mentions no files or tests to run.

Written by the indexing model from the issue text.