Stuck on the switch statement

Question

Anyone know how I might go about the following code
correctly? I need to avoid loops, so it's a little tricky for me.
Need control over playing one movie, then the next, then the next.
Eventually, I each case may have a video to play, text to display,
or another swf to load.
Thank you!
== "Code-ish"
var connection_nc:NetConnection = new NetConnection();
connection_nc.connect(null);
var stream_ns:NetStream = new NetStream(connection_nc);
my_video.attachVideo(stream_ns)
var videosArray = ["../videos/video1.flv",
"../videos/video2.flv", "../videos/video3.flv"]
switch(videosArray) {
case 1 :
stream_ns.play(videosArray[0]);
break;
// when video is done, move onto next case
case 2 :
stream_ns.play(videosArray[1]);
break;
// when video is done, move onto next case
case 3 :
stream_ns.play(videosArray[2]);
break;
// when video is done, move onto next case
};

Answer 1

Great!
Thanks for the insight. I appreciate that.
David
stiller (at) quip (dot) net
Dev essays:
http://www.quip.net/blog/
"Luck is the residue of good design."
"FlashTastic" <[email protected]> wrote in
message
news:e25oh9$47f$[email protected]..
> Hi David,
>
> I've used both methods myself, I usually use the
NetStream.time method
> when I
> have a seek bar built into the app although I find it
can be a bit
> unreliable
> when using FMS (v1.5) recorded FLVs under a minute long.
>
> I know that there can be a problem with the metadata in
FLVs recorded with
> older versions of FMS where the stream length is
reported improperly
> (which has
> since been fixed), but since I haven't run into anything
that generates a
> sequence of events in the same order (stop, empty,
flush) I would say it's
> reliable.
>
> Cheers,
> FlashTastic
>
>
>