Oops, thanks for that - seems the results from the first run of the example somehow got lost in the final version and I didn't notice.

The order of the output is dependent on when each call finished - they run in parallel, so it's not guaranteed that functions will end in the order they were invoked.

Ah yes, so they do. My lack of sleep is showing!

For some reason I was thinking the readdir would run in series so output would go up by ~1s each time.

I'd like to see how you cut bread with a gun or a fork.

I'll just use a concentrated laser to cut my steak! And char broil it at the same time!

Why is the phase not even mentioned in the article?

This. Phase is the most important subtle point about the FT that everybody misses the first time around.

The Fourier Toy mentioned in the article: http://toxicdump.org/stuff/FourierToy.swf

Notice how you can click and drag to change the size and initial phase of the circle widgets. Try changing the initial phase of any of the larger components without changing the size and see what happens. It goes haywire!

The first FT toy that I wrote years ago also ignored phase. It took me forever to figure out why my reconstructed images looked like crap.

Turns out you can't just throw away half of your transform data (you get frequency and phase for each component you care about) without being fabulously clever.

> In the brand new Visual Studio 2015 keyboard support has been dropped so that we could focus on delivering state-of-the-art handwriting recognition algorithms so that you can easily develop even the most complex applications with nothing more than a single finger or a stylus.