Hi, use: * xray -> osflash.org/xray * a logger -> also in xray or one of the other available loggers * assertions (detect and throw errors at runtime) * visible runtime exception handling
With respect to the last part, see http://objectpainters.com/blog/?p=32 The main idea behind that last point is something I find very useful, normally when you use Flash's exception mechanism, as in throw new Error ("Boe"); nothing shows up if you don't handle and catch it. We use a custom error class which prints messages on the screen if the errors are not caught. Kinda like how the new flash player does it, but then for as2. In addition the assertions are something I use very often. Eg, If you are sure that loading of that specific xml file cannot go wrong and should parse without any problems, why not assert it? greetz JC On 7/10/07, Marcelo Wolfgang <[EMAIL PROTECTED]> wrote:
Hi all, I have the type of problem I hate the most when developing flash. My swf works fine locally, but it doesn't work at all on the web. And I'm about as clueless one can be about debuggin this kind of problem. So... can anyone spare some advices? TIA Marcelo Wolfgang _______________________________________________ [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
