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!

Today, I’m releasing FlpTree 1.4.0. Changes:

• Added dropenabled, which allows dropping nodes from outside, but not dragging inside the tree (if you want that, set dragenabled to true);
• Fixed a refresh bug ([Fault] exception, information=TypeError: Error #1006: getItemAt is geen functie.Fault, refreshTree() at Node.as:501);
• Added dragEnabled per node;

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

Today, Windows (Vista) bugged me about an important update, which I should install. Well, all right, if you really want, I’ll install it… the question is.. how, WHERE IS IT!!!

windows update fail

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.

The default flex combobox has keyboard navigation support, but it’s not how you’d expect keyboard support to be. For instance, if you have a list with the following items: ‘aa’, ‘ab’, ‘ba’, and you first press ‘a’, and then ‘b’, a windows combobox would select ‘ab’, whereas the flex combobox selects ‘ba’. This is because the flex combobox only checks the first letter of a list item and handles every keypress as a separate action.
The alternative combobox handles like a windows combobox and selects ‘ab’. Feel free to download and use it in your projects.

Example:

Download: ComboBox.as

When you’re working on an Air project in Flex, and you want an alert to popup, you have a problem. Air doesn’t come with an ‘aired’ version of the Flex Alert. The flex Alert is fine, as long as you work with a single windowed application. As soon as you have more than one window, the Alert of Flex becomes more or less useless. Since you’ve got more than 1 window, Flex doesn’t know which window to make the parent window, so a model alert isn’t possible anymore.
I’ve taken the code from the mx.Alert and rewritten it to an AirAlert. It works exactly as the normal alert, only now it creates a window instead of a Panel / Titlewindow.

Usage: AirAlert.show(‘Test Alert!’, ‘Test Alert!’);
(The same as a normal alert )

Notice: I didn’t copy the Alert.YES / Alert.NO stuff, so you have to use those from the Alert class.
Notice2: You’ll find no license or whatsoever, just use it as you like.

Download / View the source

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

It’s been a while since my last post, and that’s because I’ve been quite ‘busy’ the last two months. First of all, I had a holiday to Chile, which was fantastic. And second, because I’ve decided to quit my job at theFactor.e, and start my own company, called BS10. Starting your own company takes a lot of time (at least in the Netherlands it does), so I had little time to write and update my components and stuff.

I work together with 2 other freelancers, Danny Ruchtie of Noa Media and Matthijs Wit of Functioneel Wit. Together, we make an allround team of designers and developers, capable of fulfilling almost every desired site or application.