If you only use SWF Tools and its players via CCK or the input filter then this will not affect you!

If you access swftools from PHP via the external swf() function then this should all pass you by with no impact.

But if you call in to any other SWF Tools functions then there are huge changes and before installing any updates to SWF Tools you should read this!! Or if you have written anything that implements a player or embedding method for SWF Tools this will affect you as well.

In the past SWF Tools created various arrays and objects, and these were shunted around to functions with variable numbers (and orders!) of parameters.

I've taken the plunge to parcel everything up in to a single array that collates everything about the content that is in the process of being rendered. A bit like how Drupal generally does stuff elsewhere.

The advantage is you only ever have one parameter, the array of data in progress, and it means we can now comfortably use drupal_alter since we have just one argument to pass.

I had always had this on the TO DO list, but the module is tidying up so nicely, and with an eye on SWF Tools 7, I decided to go for it.

So, if you call in to SWF Tools functions through any route other than via swf() your code will need changing.

If you have another module that interacts with SWF Tools, or implements methods, then you will need to change it. The changes are quite simple - you will still get all the parameters you had before, but instead of getting, say $vars, $methods etc you will get everything in an array with keys of 'vars', 'methods'. So it's quick to fix, and I'll document it properly hopefully, but please be aware!