Jozef Chúťka's blog » Error

Quick Tip: Constructor Of Property With Namespace

Jozef Chúťka — Fri, 18 Mar 2011 16:41:12 +0000

Some of you may not like the solution (including me) but sometimes you need a little hack to make things work for you. In my case I required a constructor of property declared under custom namespace but not defined (null). Normally, you would go for describeType(), but guess what, yeah it just does not describes properties with namespace other than public. While there was nothing better in my mind than passing some unexpected value and expect what happend I decided to go for it. Luckily an exception was thrown with correct constructor name.

Error message looks something like this:

TypeError: Error #1034: Type Coercion failed: cannot convert true to valueObject.SomeObject.

lets parse it:

import com.adobe.fiber.core.model_internal;

var item:SomeUltraCleverObjectWithNamespacedProperty
var className:String;
var constructor:Class;
try
{
    item.model_internal::["_internal_" + name + "_leaf"] = true;
}
catch(error:Error)
{
    className = error.message.toString().match("([^\\s]+)\.$")[1];
}

constructor = getDefinitionByName(className) as Class;

You should be careful about using it, because constructor is parsed from an error message that is localized (part of flash player). It may happen that in some translations the constructor name may appear in different part of the message (example parses at the end of sentence before dot “.” character).

WordPress SyntaxHighlighter Evolved goes Error

Jozef Chúťka — Thu, 28 Jan 2010 10:44:49 +0000

After latest SyntaxHighlighter plugin update (version 2.3.8), there suddenly appears error window while mouse moving over SyntaxHighlighter code:

Error #2044 & text=Error #2036 Load never comple

The problem is in clipboard.swf file loading as icon (copy to clipboard). There are more people complaining on this error behaviour, and there is a simple fix. Replace this file in your wordpress:

wp-content/plugins/syntaxhighlighter/syntaxhighlighter/scripts/clipboard.swf

For this one clipboard.swf. And its working nicely again.

Facebook application type web goes 104 Incorrect signature

Jozef Chúťka — Fri, 06 Nov 2009 10:00:16 +0000

When creating flash / flex application for facebook, Application Type “Desktop” will work for you just fine, even when your app is deployed. My app is both embedded via iframe in facebook and standalone application (not in facebook). First I tought desktop mode is just to test my app locally and when finished, I should switch to web type. But guess what, after switching to “Web” type, my standalone application refused some actions (upload photos etc.), resulting in error:

error_code: 104
error_msg: Incorrect signature

So, I switched back to “Desktop” and both iframe and standalone applications works fine. Correct me if I am wrong, but it seems, desktop application type works for facebook flash / flex api in all cases.

Quick tip: Flex Builder already appears to be running.

Jozef Chúťka — Wed, 04 Nov 2009 15:52:53 +0000

Flex Builder already appears to be running. Running two copies of Flex Builder at the same time is not recommended. Are you sure you want to continue? [ Ok ]

… and you do not see one? In windows, open task manager, find javaw.exe and end task.

Flex Error #1034: Type Coercion Failed: Cannot Convert *** to mx.core.IFlexDisplayObject

Jozef Chúťka — Mon, 26 Oct 2009 16:10:11 +0000

When you keep getting:

Flex Error #1034: Type Coercion Failed: Cannot Convert *** to mx.core.IFlexDisplayObject

… after using getDefinition() method, in my case:

// url = "../some.swf"
var request:URLRequest = new URLRequest(url);
var context:LoaderContext = new LoaderContext();
context.applicationDomain = new ApplicationDomain(ApplicationDomain.currentDomain);
loader = new Loader();
loader.contentLoaderInfo.addEventListener(Event.COMPLETE, assetsComplete);
loader.load(request, context);
...
// assetsComplete()
var applicationDomain:ApplicationDomain = assetsLoader.contentLoaderInfo.applicationDomain;
var assetsClass:Class = applicationDomain.getDefinition("Assets") as Class;
...

The problem is, in fact, the security not coercion! Try move your .swf (the one that is beeing loaded) into the same directory where master .swf file is located.