Hello, I'm working on a very simplified pyramid image viewer. The purpose of the class is to take a number of image files, load them in, make the smallest one visible and available to scale, and then every time an image is scaled up or down to the point where it matches or exceeds the dimensions of the next largest or smallest image, the viewer switches the visibility to that image, making it consistently appear as though the image is at its normal screen resolution and has not been resized or shrunk.
Right now, I'm using LoaderMax to try and load the images in. I'm able to successfully load them in, store them in an array, and add them to the stage. The problem appears to be when handling the scale event, there is some slowdown, most frequently at the larger image sizes, and quite often a crash.
When I observe the application's behavior in Adobe Scout, the DisplayList rendering seems to be taking the lion's share of the processing during the slowdown, and of that, specifically "Decompressing Images" takes the most of the DisplayList Rendering processes.
This latency when scaling does not appear to happen when using Flash's default loading processes, but then it's slow and tedious and we're trying to switch our framework to LoaderMax anyway. Is there any reason I'm seeing this weird latency with scaling the images once loading? Does the report that "Decompressing Images" is taking up a lot of processing in Scout point towards the problem? Is this a setting issue that could be changed?
I'm using a LoaderMax object to load the queue, and for the ImageLoader I'm giving it a simple LoaderContext where the only property set is "ImageDecodingPolicy.ON_LOAD"