It seems like this is quite a common problem and I found a number of blog atricles referring to it. It seems that one gets this error due to the following reasons:

• Having an incompleted switch statement without any cases
• Missing a semi-colon after a variable declaration
• Listing a twice with different extensions in your mxml
• Declaring an import twice in an Actionscript file or embedded Actionscript in an mxml file
• If certain lines of code are commented out resulting in a trace statements being unreachable

However, the reason why I was getting the error was because I had mistakenly extended a class of itself…eg

public class myClass extends myClass
{

}


AMATUER HOUR!!!

I found that soultion in a commet by Jules on Michael Imhoff’s blog.

I just had the same error (Uncaught exception in .log, java.lang.StackOverflowException). It appeared after I’d done some work with sed on my object model. Turned out one of the classes extended itself, ie class myClass extends myClass

Thanks dudes

One would think that the Flex compiler would have identified this and given a more dexcriptive error message?

buttonMode=”true” mouseChildren=”false” useHandCursor=”true”

Here’s an example of a Label which is used as a link:

< mx:Label text="Log out" buttonMode="true" mouseChildren="false" useHandCursor="true" click="logout()" />

It seems like it’s a pretty common problem and these two articles showed me the light of day, thanks dudes!

• http://frankieloscavio.blogspot.com/2007/08/mousechildren-and-buttonmode.html
• http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&productId=2&postId=1687

One of the things I have been working on is a FAQ section for a web portol. To implement this I have used the following components and controls:

1. A basepage
2. A standard mxml Tree contol ()
3. A custom ItemRenderer
4. A custom DataDescriptor
5. A function which is executed upon creation (creationComplete=”initTree()”)

The focus of this tutorial is however on Item 3, a custom ItemRenderer. So here goes…

Firstly the data structure that I am using is a standard xml file which has categories, an answer and a question, I have included an exmaple below:

< ? xml version="1.0" encoding="UTF-8"?>
< faq xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
< category>
< nameGuidance
< item>
< question>What is the meaning of life, the universe and everything?
< answer>42
< /item>

Secondly, the Tree control has a number of paramaters which need to be included to get the desired result:

< mx:Tree id="myTree"
styleName="faqList"
wordWrap="true"
itemClick="tree_itemClick(event);"
width="100%" height="100%"
top="20"
dataDescriptor="{new TreeDataDescriptor()}"
itemRenderer="renderers.TreeRenderer"
creationComplete="initTree()"
/>

I will try to cover the dataDescriptor, itemClick and creationComplete in other posts, but for the time being, the ItemRenderer works something like this:

• It is important to include the if (super.data) logic otherwise the application will through errors because it’s referring to an object with a null value.
• In the data method, I have set all parents (depth == 1) to have a bold style otherwise the nodes should just have normal font weight.
• In the updateDisplayList:
  1. I firstly remove the disclosure icons from all nodes
  2. Add some default text styling to nodes, which sets the selected node back to its original styling after it was selected
  3. Then if a 2nd level node is either highlighted (isItemHighligthed) or selected (isItemSelected) I change styling, display the disclosure icon and adjust the position of the disclosure icon
     (super.disclosureIcon.x = super.width – 50;).
• Note: The moving the position of the icon is relatively simple, but I had difficulty finding information on the web about how to do this, so I’m hoping this will help someone out ther. This particular example moves the disclsure icon 50px inside the right hand border of the Tree control

package com.g3global.ipp.view.components.renderers
{
import mx.collections.*;
import mx.controls.treeClasses.*;
import mx.controls.listClasses.ListBase;

}
}
}
}

So that’s about it. Unfortunately I can’t link to a working demo of this feature because it is part of a much bigger application which is being built for a client.