Any browse or save as dialog can only be triggered by user input (keyboard or mouse(click)). And this makes sense, you don’t want an ad to popup thousands of ‘browse’ windows. But I cannot see why this same security measure is taken for doing a multipart request. Why sould user interaction be needed to upload, say a bytearray, to the server. This bytearray could easily be generated from a bitmap(data), so no browse for file window is needed.

This error came up in an application which displays a small photo. The user can upload a photo to the server. This server is somehow not capable of resizing images, so the uploaded image is downloaded to the flash again, resized in flash and send as a bytearray to the server again.

This worked perfectly in FP < 10, but now, there has to be some interaction to do the second upload. We worked around this by having a small popup asking the user if the uploaded picture is the correct one. Works also, but it’s just a work-around, not a solution.

I talked about this issue with James Ward of Adobe, and he also didn’t see why this security has been taken. So, I’ve created a feature request in the bug system of adobe, located at https://bugs.adobe.com/jira/browse/FP-978. Please vote if you think this is a ridiculous security measure and should be removed!

Thanks!

Ow and by the way: right click to see the source and find out how it’s done.

The source seems to be fucked up, here’s the relevant code: http://experiments.flexperiments.nl/3dtext2/srcview/source/experiments/flexperiments/text3d/Text3dFXApp.as.html

Cool huh? You can change the text by altering the text in the input field (topleft corner). I’ll be tweaking this little thingy a bit further to increase the performance.

Check it out here: http://www.closier.nl/blog/?p=77

• 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.

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

You can compare this tool with the debugging options and object inspector of flex, but you now have the possibility to edit all the objects’ variables (only strings, numbers and booleans though) in real time.

How does it work?

Easy!

1. First, download the ASDebugger.swc and the ASDebugger as .exe or .swf (air version will follow on demand);
2. Include the swc file in your flex or flash project;
3. Place a debug statement like this: ASDebugger.debug_prop(<any object>) anywhere in your code;
4. Fire up the debugger;
5. Compile your project;
6. See what it sends to the ASDebugger, change the values you want to change, see your changes immediately!

How do I get it?

You can download the neccessary files from the ASDebugger project page.

Is it free?

For now, yes. But I’m not sure if future versions will be.

I have a question / found a bug / want to request a feature

Please leave a comment on any of the ASDebugger related posts on this blog (this post for instance ). Do let me know what you think!.

I wanna see an example!

Here you go:

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!

And here it is:

Use this swf to test it:

Now, there are some limitations to this debugger. For instance, you cannot send MovieClips to it, it will simply always return ‘undefined’.

Also, there’s a limitation to the size of an object, it may no exceed more than 64k.

To download it, go to the ASDebugger download page.