OK, just did a bit more testing with firebug. I can confirm the COMPLETE events are fired when the first request images complete loading as well as the screen has to wait for the previously requested images to load before it starts on the new ones.
I really need a killStream function or something to get around partially loaded images continuing to load in the background. Any suggestions?
I don't believe it's possible to abort the loading of an image once it's been requested from the remote server. You need to make your application a bit more sophisticated to deal with that. If you don't want them seen make them invisible and remove them when loaded.
Thanks for the reply pauland. I was affraid there might be no way of stopping them
My issue isn't that they are SEEN, it's the fact they are still loading and regeistering events on 1 visual element.
<mx:Image id="img1" complete="onCompleteHandler()" />
img1.source = myImgURL;
Then, while myImgURL is still loading, user clicks next:
img1.source = null;
img1.source = newImgURL;
Even though I've replaced the source of img1 to newImgURL, the onCompleteHandler still fires when myImgURL has completed loading, not waiting until its current source, newImgURL, has loaded.
*sigh* Looks like it might be back to the drawing board for me.