Today, I’ve spent the entire morning fixing a strange error in a Flash Project with Away3D. Every now and then, it would give me the following error: Error #2007: Parameter bitmap must be non-null. It would give the error when calling the render function of the view.
The strange thing is that it would never give the error when running in debug mode, making it very hard to find the cause of the error. Eventually, I found that Away3D is not very fond of objects with alpha set to 0. Setting it to 0.01 made all the errors magically disappear. For me, this is fine, but I can imagine scenario’s where this is not a suitable work-around, so I’ve also reported it to the away3d devvers.

I’ve updated the ASDebugger. Not much news here, I only implemented an updated (less buggy) version of the FlpTree. You can download the debugger on the project page.

I’ve just released ASDebugger version 2.1. Some minor bugs are fixed, like:

• You can now edit any movieclip from the displaylist, not just the deepest ones
• Copy all to clipboard now works as expected
• Scrolling a numeric stepper only scrolls the stepper, not the tree
• It’s now possible to close root nodes
• The console scrolls with the content

And some features are added:

• Copy an object as JSON string (only works for simple / small objects)
• Re-added legacy support for our old (in-house) TFEDebugger

For this update you need to update both the SWC and the SWF / EXE file! But there’s backwards compatibility both ways.

And it’s available at the project page, now.

Yeah! It’s here, the long awaited update for my debugger. And since I’ve added a lot of new functionality, I decided to raise the major version number (easy decision to make when you’re the only developer on the project ). So, what does it do? Well, a small list:

• Send traces / strings
• Inspect objects, movieclips, displayobjects and alter their values.
• Browse through the displaylist of any (flex or flash) application. more…

When you’re developing an Actionscript project – Flash or Flex – you cannot live without a decent debugger. Flex provides quite a good debugger and the Flash IDE has also a reasonable debugger. The problem with those debuggers is that you have to build explicitly for the debugger. So when you’re deploying on a remote server, you don’t have those debug options.

The ASDebugger allows you to trace variables. It has support for strings, integers, arrays, dates, arraycollections, objects and everything in between.

Usage is simple, import the asdebug.as class in your application and call the debugger:

import nl.flplibrary.debug.ASDebugger;
import mx.collections.ArrayCollection;	
 
private function simpleDebug():void {
	ASDebugger.debug("<b>test</b>");
}
 
private function advancedDebug():void {
	var o:Object = new Object();
	o.my_string = "<i>string</i>";
	o.my_number = 123.456;
	o.my_int = parseInt("1");
	o.my_array = ["item 1", "item 2", "item 3"];
	o.my_arraycollection = new ArrayCollection([{label:"item 1", data: 1},
												{label:"item 2", data: 2},
												{label:"item 3", data: 3}]);
	o.my_object = {	label1:"item 1", data1: 1,
					label2:"<i>item 2</i>", data2: 2,
					label3:"item 3", data3: 3};
	o.my_date = new Date();
	o.my_xml = new XML();
	o.recurse = o;
 
	ASDebugger.debug_prop(o);
}

Before running the application, startup the ASDebugger. The ASDebugger comes in different flavors:

• In a .exe projector file;
• In a .swf;
• As an AIR application;
• or you can even use the ASDebugger on this page! more…