flash (macromedia): The description of the random problem sounds like a data communications sync
problem where on a speedier bandwidth you will not see but over the internet
has a greater chance of occurring.

Not sure of the details of code, but if the loader swf is performing AS
tasks for or with the loaded swf before the loaded swf arrives then you need
to use something like MovieClipLoader to assure the loaded swf is in place
before your container swf tries to use it via AS.

--
Lon Hosford
www.lonhosford.com
May many happy bits flow your way!
[quoted text, click to view]
HI all --

I've got a real head scratcher here. I developed a Flash training course,
and
tested it on my web server. Then, when I uploaded it to the client's web
server, a key behavior broke.

You can see the working version at

http://www.cecosweb.com/offerings/SPP/

The feature that broke is the closed captioning. The course consists of a
persistent "frame" SWF at _level0 that loads successive pages of the course
(other SWF files in the same directory on the server) into a higher level.
There is a "closed captioning" box in the frame SWF. Each screen SWF loads
text into it with some action script in its first frame:

_level0.CCaption_txtArea.text = "blah blah blah";

When the SWFs are hosted at my web server this always succeeds. When the
SWFs
are hosted on my client's web server, it usually fails, though on about 1
screen out of 10 at random, it succeeds.

I don't understand how it could behave differently from the two web
servers,
since they are both loading the exact same SWFs into the exact same Flash
Player.

I authored in Flash MX 2004 Professional, targeting Flash Player 7. I am
viewing in Internet Explorer 6.0 on Windows, with Flash Player 7,0,19,0
plugin.

Thanks in advance for any help or ideas,
Bob

HI all --

I've got a real head scratcher here. I developed a Flash training course, and
tested it on my web server. Then, when I uploaded it to the client's web
server, a key behavior broke.

You can see the working version at

http://www.cecosweb.com/offerings/SPP/

The feature that broke is the closed captioning. The course consists of a
persistent "frame" SWF at _level0 that loads successive pages of the course
(other SWF files in the same directory on the server) into a higher level.
There is a "closed captioning" box in the frame SWF. Each screen SWF loads
text into it with some action script in its first frame:

_level0.CCaption_txtArea.text = "blah blah blah";

When the SWFs are hosted at my web server this always succeeds. When the SWFs
are hosted on my client's web server, it usually fails, though on about 1
screen out of 10 at random, it succeeds.

I don't understand how it could behave differently from the two web servers,
since they are both loading the exact same SWFs into the exact same Flash
Player.

I authored in Flash MX 2004 Professional, targeting Flash Player 7. I am
viewing in Internet Explorer 6.0 on Windows, with Flash Player 7,0,19,0 plugin.

Thanks in advance for any help or ideas,
Bob

It was a shot. It rings of timing problem. Perhaps the serverside code is
not checking for a data failure before communicating with Flash.

You might need to add a dynamic text field to float over or near the edge of
the movie and use it for output window over the net to trace some variables.


--
Lon Hosford
www.lonhosford.com
May many happy bits flow your way!
[quoted text, click to view]
Thanks for the initial thinking Lon, but I think I'm already handling those
aspects well --

The parent SWF uses the Loader component to load the children. Each child
SWF
has a stop() action in Frame 1. Only after the Loader reports that the
child
is 100% loaded does the parent issue a gotoAndPlay(2) to the child. That is
working reliably.

Also, I am getting faster downloads from the client's site, where I have
problems, than from my site, where I don't. (My web server is not located
in
my home.)

Thanks!
Bob

Thanks for the initial thinking Lon, but I think I'm already handling those
aspects well --

The parent SWF uses the Loader component to load the children. Each child SWF
has a stop() action in Frame 1. Only after the Loader reports that the child
is 100% loaded does the parent issue a gotoAndPlay(2) to the child. That is
working reliably.

Also, I am getting faster downloads from the client's site, where I have
problems, than from my site, where I don't. (My web server is not located in
my home.)

Thanks!
Bob