I had a similar problem (onInit firing when it actually failed) and I
found that checking the bytes loaded vs bytes total worked as a way to
check if it really succeeded or not.
-Andy
On 2/14/07, Danny Kodicek <[EMAIL PROTECTED]> wrote:
> On 2/14/07, Danny Kodicek <[EMAIL PROTECTED]> wrote:
> > > I thought I saw this discussed recently, but I couldn't find
> > > it in the archives. Apologies if I'm repeating something.
> >
> > You might be thinking about the thread I started with the
> opposite problem:
> > onLoadInit was called when the load actually failed.
>
> Ahh, right. Ever find an answer to that?
The best I came up with was this (set fileExists to true first):
function onLoadComplete(tContainer:MovieClip, tStatus:Number) {
if (tStatus >= 300 || tStatus < 200) {
fileExists = false;
}
}
function onLoadInit(tContainer:MovieClip) {
if (!fileExists) {
this.onLoadError(tContainer);
} else {
// succeeded: do stuff here
}
}
Foolproof? I doubt it. But it works so far.
Danny
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
