Great post, it really helped me out but i ran into another problem i can not figure out so far. If you listen for the SELECT_MULTIPLE event you receive an event object with a property “files”, which is an array that in turn containts File instances…not MyFile objects, even though the original object firing that event was of the MyFile type.

Am i running into a technical limitation here or just missing something? I fear the former, i hope the latter.

Cheers from the Netherlands!

Hehe… I was waiting for someone to ask that.

Basically, I needed to associated from meta data with an image that I had written to the file system. I could have created a value object that contained the file path and the meta data, but:

1. seemed like overkill when I could just store the file reference
2. I was worried about the value object getting out of sync with the file system

Plus, it makes the code a little cleaner when I am serializing and de-serializing objects.

You can view the code here:

http://onairbustour.googlecode.com/svn/trunk/projects/AIRSnapshot/src/

To be honest, im not sure if this is a “best practices” sort of thing, but regardless, the technique works for other classes also.

mike chambers

mesh@adobe.com

just wanted to know, why you want to (de-)serialize a File-reference?

Greetz