Today I’m releasing a new version of my Tree. Most parts are rewritten for way better performance.

This tree is a replacement for the standard flex tree, which is buggy, slow and not very customizable. With version 2.0, you have full control of the source, so you can tweak it to your needs. It has all the functionalities of the 1.4 version, but some of the stylenames have got another name to match the general stylenames of flex (eg. selectionColor), see the docs for that.
Usage:

<tree:FlpTree
	x="100"
	y="100"
	open="_openCheck(event)"
	close="_openCheck(event)"
	width="250"
	height="400"
	openNodeOnHover="true"
	hoverDelay="150"
	dataProvider="{adata}"
	borderColor="#000000"
	borderStyle="solid"
	borderThickness="1" />

If you find a bug in the source, please leave a comment to let me know!

Here’s what you’ll need:

• The source
• The compiled source (swc)
• The docs

Have fun!

Note: This component is written for Flex 3, it’s not tested on Flex 2 nor Flex 4!

I’ve been awful quiet on my blog lately, time to do something about it .
First off, I’m releasing version 1.3.0 of my tree component.
I’ve added a filterfunction, which behaves just like a normal filterfunction, but works recursively.
I’ve also fixed some minor bugs, some events weren’t dispatched correctly.
And last but not least, I’ve made the displayobjects in the defaultrenderer protected instead of private, so you can access them more easily when extending the defaultrenderer.

You can download the new swc from the project page, which is here. Also, a link to the docs and an example can be found on the project page

Just fixed the drag & drop bug. It’s now possible to drop between nodes again.

You can download the new swc from the project page, which is here. Also, a link to the docs and an example can be found on the project page

Finally!!!! I nailed the height bug! So, now you can finally make advantage of the variable row height! After a lot of searching, setting debug statements and all other debugging stuff, it turned out one event was called a bit too much which caused flex to seriously fuck up. Still can’t find the exact reason for it, but removing the listener did not harm the tree at all, so it was useless anyway .

You can download the new swc from the project page, which is here. Also, a link to the docs and an example can be found on the project page

Have fun!

Formerly known as the IKTree, FlpTree has an updated version. This new version has several bug fixes and the overall performance is improved. Changes since the last version include:

• FindNode(s) works now properly;
• Selection and multiselect now works
• Performance tweaks
• Other bugs which I forgot about
• Added open on hover more…

I’ve made some changes to the tree, which add some more functionality and make it even more (re-)usable.

IKTree now has:

• Caching / Recycling of children, which reduce the ‘flickering’
• Label & IconFunctions
• Object access for labelfields. You can now access objects in the tree for the labelfield. For instance, you can set ‘obj.label’ as labelField. It will then set the label as data[obj][label].
• Doubleclick support
• Added some styles (indicatorThickness & indicatorColor)

more…

Today I’m releasing the first version of my tree component. This component is a substitute for the build-in tree of flex. Why? Because the build in tree is build on the list classes, which aren’t the most stable classes of flex. My tree is build entirely with UIComponents and VBoxes, no list class used here. more…

That’s right, I was so fed up with the tree component of flex, that I decided to build my own. And to make sure that it will not end up as crappy as the default one, my goal was to make sure no listclass or whatsoever would be used.

more…

I just ran into another strange behavior of flex. Lets say you have a VBox, with an image inside. When the user clicks the image, it should do some stuff, but when the user clicks (mousedown actually) the VBox it should start dragging. You would expect that when you click the image, both events are fired. This is true when you don’t invoke the dragmanager. If you call the dragmanager, it cancels out all further mouseEvents, thus preventing the code of the image clickhandler to execute. more…

Sometime ago a wanted a tree with all different kinds of icons, depending on the type of the branch. Flex has some support for this, but only for embedded images. The problem was that I couldn’t use embedded images because the images are loaded dynamically from a database. So I had to find a way to fool flex, and the solution is quite simple. more…