> Where does the debug player send the output is it the normal stderr > and stdout?
No, a popup dialog box. (Which is extremely annoying (*) - if anyone knows a way to have it just log the exception and then ignore it please let me know.) Darren *: First because script actions freeze until I press the button, messing up the timing problem I'm trying to track down, second because copy and paste doesn't work in the dialog box, so I have to scribble the error down myself, and third because it means I cannot put it on a production box. Murphy's Law states: there is always at least one bug that can only be reproduced on a system that the developer has no direct access to. :-) > > Glen > > Darren Cook wrote: >>> Admittedly I have only tried this with an http url, which I am >>> guessing is maybe not "streaming", but it should not cause my app to >>> hang... I even tried messing with the buffer size - still no change. >>> >> >> Are you running the debug player; it tells you about the uncaught >> exceptions that get thrown whereas the normal player just quietly >> swallows them. Perhaps the "hang" is due to something else. >> >> Or, catch the NetStream.Buffer.* events and log them (as well as >> NetConnection.Connect.Success), and, if not already, make sure you are >> catching NetStream.Play.StreamNotFound and reporting it as an error. >> >> Darren >> >> >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org -- Darren Cook, Software Researcher/Developer http://dcook.org/mlsn/ (English-Japanese-German-Chinese-Arabic open source dictionary/semantic network) http://dcook.org/work/ (About me and my work) http://dcook.org/blogs.html (My blogs and articles) _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
