Complete Event fires before last image is ready as blob

[johnmastri]

I created a manifest of images to load which calls handleImagesLoadComplete when complete. At this point it shows that the last image has, in theory, been loaded (queue.getItems()). However when createGrid() is called, which pulls in the images, the last image shows as undefined. I have been able to resolve this by adding a slight delay to, I'm guessing, compensate for the time it takes to convert the last image into a blob. Any idea what else it could be?

loadImages : function() {

        var queue_manifest = [];

        for(var a = 0 ; a < this.data.projects.length ; a++) {

            var d = this.data.projects[a];
            for(var b = 0 ; b < d.content.length ; b++) {

                var c = d.content[b];

                queue_manifest.push({
                    src: "image/case_studies/" + c.img
                })

            }

        }

        AP.queue.reset();
        AP.queue.on("complete", this.handleImagesLoadComplete, this);
        AP.queue.loadManifest(queue_manifest);

    },

    handleImagesLoadComplete : function(event) {

        event.remove();
        this.createGrid();

         //hacky fix - only shows the last image when a delay is added
        //$t.delayedCall(.1, this.createGrid, null, this);

    }

[lannymcnie]

This is odd behaviour because we use an async onload on the newly created image before dispatching complete on the image -- and the manifest does not complete until all its items are completed. Worth looking into more.

[Honga1]

Not sure if this is related. I had a case where my queue construction routine was initialised twice ( new LoadQueue, assets in the manifest, and load routine called). One interesting side effect of this is that when listening to the 'progress' event of the loader, it would go past the end value of 1 to around 1.4.

I was first able to fix this by adding a delay of 2s. Then I found the double creation of the queue. It confuses me however, as I don't know what part of it would bleed into global scope to confuse the other.

The 'complete' event was fired prematurely when the 'progress' value reached 1, but the files were indeed not ready to be resolved with getResult. I should add this was for png/jpg image resources.