Hmm ... not sure what you thought I was saying csuwldcat. I use Assets.images in -more to load up the images, which uses the map () function in -core, which uses the 'for' loop I quoted here--so I'm certainly not going to go tinker with the map function in -core.
That is good information though. So it appears that Asset.images will always progress, progressively, stratboy. On May 26, 12:44 pm, csuwldcat <[email protected]> wrote: > The for loop is an in-order loop, there are loops that return an > inverse set of the data, for instance: the --while loop would be much > faster on large datasets, but you need to flip the order after. > > On May 25, 5:46 am, stratboy <[email protected]> wrote: > > > > > Hi! > > > suppose this code: > > > this.images = new Asset.images([ > > this.o.topLeft,//path > > this.o.topRight,//path > > this.o.bottomLeft,//path > > this.o.bottomRight//path > > ],{ > > onProgress:function(counter,index){ > > console.log(index); > > } > > }); > > > Well, it seems to always trace out 0,1,2,3. BUT: can I be really sure > > that it will ALWAYS do it? Will it always load the images exactly in > > the order found on the passed array? > > I need to know this, because if true, I can then write a method that > > sets my elements on progress without the need of other checks. > > > Anyone knows? Bye!
