[quoted text, click to view] "Mr_Interweb" <webforumsuser@macromedia.com> wrote in message news:e43qn9$obc$1@forums.macromedia.com...
>I have no idea what's up with that loader. I tried it out on 6 different
> computers today on windows and mac. It was working this afternoon. The only
> thing I can find is that my loader is getting cached in IE when I cleared out
> the cache things worked fine. If things are still fishy after a cache clear or
> trying in out in Firefox, try skipping the preloader:
>
>
http://ultimatewindowtinting.com/tinting-tool/tinter.swf >
> The app will scale weird in the browser without the loader, but you can at
> least see it.
>
> By the way, thank you for telling me about the errors you found with that
> loader. It is the most bizarre issue I have ever seen.
That's very interesting how you got that color selector to work. good one!
I took a look at the code in your preloader. One thing that is not right is that you are looping back to frame 2 where the
onEnterFrame is created. That means that you are creating another onEnterFrame with every loop, (or wrecking the original one).
I found that if I put your file tinter.swf in my cache, then the preloader ended and the main file ran. If tinter.swf wasn't in the
cache then the preloader just gets stuck.
Seems like the loadMovieNum is failing.
Anyway, instead of that you might want to do something like this to make sure that you don't initialize onEnterFrame more than one
time..
if(!initialized)
{
initialized = true; // block this init code next time
loadMovieNum("tinter.swf", 2);
this.onEnterFrame = function () // add 'this' here
{
... etc
}
tralfaz