Beta Stage 4 is out!

The final beta of Filter Forge 2.0, Beta Stage 4, is online:
http://www.filterforge.com/download/beta2/index.html

THANK YOU Vladimir!

Have a GREAT day!

Ron

Zoltan, if memory serves, it was you who inspired us to do the Bearestroika example -- some time ago you posted a photoshopped FF screenshot depicting a "DooM" component. We liked that idea, as you see .

Hah, yeah, I remember, lol, and you pulled it off, man, you're the best.

Lua... damn... there goes my free time

Okay, FF, I think you just won.

Quote
Sjeiti wrote: Lua... damn... there goes my free time

+10 better make that +10,000

Seriously thou GREAT WORK FF CREW...Does this mean there will be a new tab for scripts kinda like snippets? Or just post in the scripts thread?

Aww nice.. and I didn't see it yesterday as it was my birthday.. very good timing FF

Happy bday yesterday Sphinx

Quote
Crapadilla wrote: What about 'polymorphic' components?

Uff... They are as desirable for us as for you, Dilla
But we've decided to cut this feature for 2.0 release.
As usual the reason is lack of time...

Quote
ronjonnie wrote: Welcome back Crapadilla! Smile Smile Smile Smile We all missed you!!

LOL ron,

no need to welcome me back everytime I switch off my lurking device.

Quote
Egret wrote: Uff... They are as desirable for us as for you, Dilla. But we've decided to cut this feature for 2.0 release. As usual the reason is lack of time...

Well, for now, depth-sorting for Bombers would suffice!

Quote
dmorrill wrote: created a filter that needed two copies of the same script component.

I had an idea of providing a place for so-called "Global Scripts", where you could define functions and initialize variables that will be visible to all script components in the filter.

Quote
dmorrill wrote: I'm also looking forward to seeing a few more details on debugging, printing and logging script information.

A quick debugging tip: you can use the Color Inspector to examine numeric values of your variables -- just return the variable as one of the RGB channels.

Quote
Vladimir Golovin wrote: I had an idea of providing a place for so-called "Global Scripts", where you could define functions and initialize variables that will be visible to all script components in the filter.

Well, that sounds good also, but I guess I'm thinking of something that would allow us to save a script component, its input definitions (and a name) as a new component that we could drag from the Components list. Right now it doesn't seem like there is any easy way to re-use a script component in another filter (unless I'm missing something).

Quote
Vladimir Golovin wrote: A quick debugging tip: you can use the Color Inspector to examine numeric values of your variables -- just return the variable as one of the RGB channels.

OK, but I hope there will also be a way to output data to the console/logging window as well. In my case, I'm getting 'nil' values when doing certain table look-ups, and I would like to know what key values are causing the problem. For now I simple check every look-up to see if it returns 'nil', and then substitute a valid value for the result. It can't be occurring in very many cases, because the result is visually correct, even with the errors. But if I don't handle the nil case, the script fails with an error. So I need the ability to display the key value causing the error somewhere. I tried calling 'print' in the 'prepare' function, just to see if it would send the data to the message log, but it didn't work.

Quote
dmorrill wrote: Right now it doesn't seem like there is any easy way to re-use a script component in another filter

Have you tried Ctrl+C on a component and Ctrl+V in another filter?

David, I'd advice to post tips like these in the Scripting forum.

Quote
Vladimir Golovin wrote: David, I'd advice to post tips like these in the Scripting forum.

OK, will do so from now on. Thanks...