Package | com.demonsters.debugger |
Class | public class MonsterDebuggerFlex |
Inheritance | MonsterDebuggerFlex ![]() |
Method | Defined By | ||
---|---|---|---|
breakpoint(caller:*, id:String = breakpoint):void
Since version 3.0 the MonsterDebugger supports breakpoints. | MonsterDebuggerFlex | ||
clear():void
This will clear all traces in the connected MonsterDebugger desktop application. | MonsterDebuggerFlex | ||
initialize():void [override]
Init the Monster Debugger
| MonsterDebuggerFlex | ||
inspect(object:*):void
This function will change the base target of the MonsterDebugger that was set in the initialize
function and send the new target to the desktop application for inspection. | MonsterDebuggerFlex | ||
snapshot(caller:*, object:DisplayObject, person:String, label:String):void
Makes a snapshot of a DisplayObject and sends it to the desktop application. | MonsterDebuggerFlex | ||
trace(caller:*, object:*, person:String, label:String, color:uint = 0x000000, depth:int = 5):void
The trace function of the MonsterDebugger can be used to display standard objects like
Strings, Numbers, Arrays, etc. | MonsterDebuggerFlex |
breakpoint | () | method |
public final function breakpoint(caller:*, id:String = breakpoint):void
Since version 3.0 the MonsterDebugger supports breakpoints. Calling this function will pause your application on that specific point. All timers, event listeners, animations, etc. will stop, but you can still inspect your application using the MonsterDebugger desktop application. Note: This function is only available when running your application in the Flash Debug Player or Adobe AIR’s ADL launcher.
Parameters
caller:* | |
id:String (default = breakpoint )
|
clear | () | method |
public final function clear():void
This will clear all traces in the connected MonsterDebugger desktop application.
initialize | () | method |
override public function initialize():void
Init the Monster Debugger
inspect | () | method |
public final function inspect(object:*):void
This function will change the base target of the MonsterDebugger that was set in the initialize function and send the new target to the desktop application for inspection. For example: This can be easy when you want to inspect a loaded SWF movie or an active window in case of Adobe AIR. The main advantage of inspect over a trace if the live browsing capabilities in the desktop application and the possibility to adjust properties and run methods.
Parameters
object:* |
snapshot | () | method |
public final function snapshot(caller:*, object:DisplayObject, person:String, label:String):void
Makes a snapshot of a DisplayObject and sends it to the desktop application. This can be useful if you need to compare visual states or display a hidden interface item. Snapshot will return an un-rotated, completely visible (100% alpha) representation of the supplied DisplayObject.
Parameters
caller:* | |
object:DisplayObject | |
person:String | |
label:String |
trace | () | method |
public final function trace(caller:*, object:*, person:String, label:String, color:uint = 0x000000, depth:int = 5):void
The trace function of the MonsterDebugger can be used to display standard objects like Strings, Numbers, Arrays, etc. But it can also be used to display more complex objects like custom classes, XML or even multidimensional arrays containing XML nodes for that matter. It will send a snapshot of those objects to the desktop application where you can inspect them.
Parameters
caller:* | |
object:* | |
person:String | |
label:String | |
color:uint (default = 0x000000 )
| |
depth:int (default = 5 )
|