Comments on: Debugging in ActionScript 3.0 – Part 1 – Trace Tutorial

By: Kasbi

Kasbi — Fri, 23 Jul 2010 17:57:04 +0000

Am going crazy with this application. I am recieving an object that as an arraycollection in it. All the other members are strings and they show up but the arraycollection does not. What can i do? Please

By: grabek

grabek — Thu, 14 Aug 2008 22:31:26 +0000

not bad – but, still comes very short to what I needed. Paul’s script – almost there, but still far far away

By: Milo

Milo — Wed, 08 Aug 2007 02:41:56 +0000

nice , exactly what i was looking for.

By: Fraser Crosbie

Fraser Crosbie — Fri, 13 Jul 2007 15:48:33 +0000

Yup, its right here:
http://www.flashdev.ca/article/trace-objects/

By: KJ

KJ — Fri, 13 Jul 2007 11:35:02 +0000

Did you write up the post about tracing the internals of the object Objects? Because it’d be really helpful.
Cheers

By: Paul

Paul — Tue, 12 Jun 2007 16:55:46 +0000

Hi,
I have actually made a as3.0 version of the as2.0 object dumper .. enjoy it here .. http://www.grafikk.co.uk/blog/archives/108

By: amacdonald

amacdonald — Wed, 26 Jul 2006 15:27:33 +0000

by the way – about creating custom trace methods, they can be creative sometimes, but they add weight, and when you do such – you cannot select Omit Traces from publish settings and have all your trace lines removed (yes, it physically removes them from compiling – if you just want to turn tracing on/off – use the verbose/none option from the actionscript window’s topright menu selection.

This is also why you do not want to ‘compile strings’ to be traced out – just add the multiple trace calls, its debug… it can run slow (most things do) in debug. When you publish with ‘omit traces’ all trace() lines are physically removed from the exported swf. Imagine a large project with tons of traces?

ex:

trace(“omit me”);
if(blah) doSomething();

if you check in a decompiler (I use ASV myself) you’d notice there is no existance of trace(“omit me”) after a publish with ‘omit traces’

keep it in mind next time you’re juggling your debug

faster, stronger, better.

By: amacdonald

amacdonald — Wed, 26 Jul 2006 07:21:43 +0000

another option for larger applications is to setup a simple dashboard you can toggle on/off via a Key object listener.

as for [object Object] not being so informative, give your classes a toString() function which returns classname and super if present…

public function toString():String
{
return “["+classname+" "+(super.classname ? super.classname : "object")+"]“;
}

add a valueOf method to dump out pertinent info (possibly an ObjectDumper return)