Maybe the high CPU usage when resizing, compared to ShowImage, is the same reason for this:
Down-scale an image with smooth scaling activated
Wave another window in front of the image
Watch the CPU usage with ActivityMonitor spike. It isn't when smooth-scaling is deactivated.
Is it filtering the whole image everytime the waved window reveals a formerly hidden area of the image?
Maybe the high CPU usage when resizing, compared to ShowImage, is the same reason for this:
Watch the CPU usage with ActivityMonitor spike. It isn't when smooth-scaling is deactivated. Is it filtering the whole image everytime the waved window reveals a formerly hidden area of the image?