Forcing code execution order in conditional statements?

Question

I don't know if the above subject line is the best description, but here is the issue.
I have created an image gallery where each "slide" is an image loaded by one UILoader component.  Everything works, except I noticed that as a user it is annoying to wait for each new slide to load.
So, even with my limited knowledge of AS3, I decided to figure out a way to load the next upcoming image before the user requests it. 
My “dirty” solution was to have 2 UILoaders – one for odd numbered slides, one for even numbered slides.  That way, when the user is viewing a slide with an odd number in the first loader, the next image can be loaded into the second (currently invisible) loader and ready to go when requested.  A “next slide” button would simply toggle the visibility of these two loaders.
Not an elegant solution, but I thought it would work.  Unfortunately, that is not the case.  The issue lies in the function that is called when the user clicks on the “next slide” button:
function nextButton(event:MouseEvent):void
imageNumber++;
            myModulo = imageNumber % 2;
            if (myModulo == 1)
                        Loader1.visible = false;
                        Loader2.visible = true;
                        loadNextSlide();
                        //where the loadNextSlide() functions loads the next image into the currently invisible loader
            else if (myModulo == 0)
                        Loader2.visible = false;
                        Loader2.visible = true;
                        loadNextSlide();
                        //where the loadNextSlide() functions loads the next image into the currently invisible loader
Say the user is currently viewing slide 3, when they click the “next slide” button, imageNumber (which was = 3) is now  = 4, and that sets myModulo = 0, satisfying the second condition.
I assumed that what would happen next was that the loaders’ visibility properties would immediately change and then the loadNextSlide function would be called.  In SIMULATED DOWNLOAD, however, it seems that none of the conditional code is executed until the loadNextSlide function runs.
This completely defeats my effort, because when the user (who, in the example, is viewing slide 3) clicks on the “next slide” button, they have to wait to see slide 4 (which is already loaded) due to the loading of slide 5.
I tried replacing "loadNextSlide();" with "dispatchEvent(new Event("loadNextSlide"));" and added an eventlistener that calls the loadNextSlide function, but I got the same result.
Is this just the nature of the AS3 language? Or, more likely, am I thinking about this incorrectly? 
If this really is the "law of the land", is there a way around it?  Is there a better way to load upcoming slides using a loader?

Answer 1

you're welcome.
i generally load everything sequentially.  if you don't want user's to possibly advance into the display far enough to see a load-delay, then you can use some preload display.  here's an example i'm doing for a current client:
www.kglad.com/Files/tf
and click portfolio.
this client has a lot of images to load and wants them presented as soon as possible so i load them sequentially.  that makes for an orderly display (though this client only wants a few images viewable on-stage at any one time).