Heheh.... I do get your reasoning, it really does seem as wasting memory, I know that. If the program wasn't so complex I would have used the setscale thing. But since not all sprites have to be mirrored things did become a little complicated. Most of the used characters as not simetric, so they have to be drawn from both sides anyway, meaning two TImages were needed anyway. Only those few who where simetric were to be mirrored this way in order to save a much work as possible (as little as it would be). Using "SetScale" would limit me to the simetric characters, or setting much complexibility in my DrawScreen routine, which is one that already contains more mathematics than my brain could take (ok, that may be an overstatement, since if it were I couldn't get this working). That's the reason why this method was chosen, and not setscale, which was my first thought as well. (Trust me, I only use up extra memory if that is the best way to go. If I didn't have to deal with as well simetric as non-simetric creatures, I wouldn't have bothered and used setscale instead).
Now the mirroring was not the most important part of my post.
It's more if that it may become possible for me to have to render more images on a semiliar way. And I was more inquiring on if all was covered in the direct in-image access. I couldn't really figure the best way out, y'see.
Now the mirroring was not the most important part of my post.
It's more if that it may become possible for me to have to render more images on a semiliar way. And I was more inquiring on if all was covered in the direct in-image access. I couldn't really figure the best way out, y'see.