Ah
Now I got it ...
That's indeed really strange ...
The behavior that should happen ... at least if working "normal", it should be drawn to all images when applied to 1 shield as all point to the same image reference.
But you say that this "backreference" happens on the pixmap step of lockimage which indicates that somehow the other images are not refreshed ...
assuming that unlock creates a new reference still does not explain, why the change of the 2nd shield "knows" of the damage to the first. if the behavior with not refreshing was meant this way, then this is the bug, otherwise the not refreshing
Are you using image:TIMAGE pixmap:TPixmap or int handles btw?
in later it might be an error with that ...
Now I got it ...
That's indeed really strange ...
The behavior that should happen ... at least if working "normal", it should be drawn to all images when applied to 1 shield as all point to the same image reference.
But you say that this "backreference" happens on the pixmap step of lockimage which indicates that somehow the other images are not refreshed ...
assuming that unlock creates a new reference still does not explain, why the change of the 2nd shield "knows" of the damage to the first. if the behavior with not refreshing was meant this way, then this is the bug, otherwise the not refreshing
Are you using image:TIMAGE pixmap:TPixmap or int handles btw?
in later it might be an error with that ...