Jacque,
This is a stab in the dark, but from a logical standpoint, could this
be happening:
1) User starts first movie
2) For whatever reason, it takes more than 250 milliseconds to
actually start playing
3) Timer sees that currentTime hasn't changed, think the movie is
done (in reality, it hasn't even started)
4) Go to second movie, repeat #2...
This might be no help if your script is more complicated (i.e. checks
the duration against the current time), but that's the only logical
flow I could think of...!
Maybe something about her machine or Quicktime Pro is taking longer
to start playing the movies? 250 milliseconds might be enough to
throw off your script, but still not human-perceived?
I'm hoping someone has a clue to this...
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
