Old Config Needs Some First Aid

Post by **BTT** » Mon Jun 06, 2011 10:19 pm

Hello All

I have found another old config (FlowField) that I remember from the past and, I would like to include this in the current version of G-Force.
The trouble is when G-Force attempts to load the config I get something along the lines of:- Error..... A0?.

Code: Select all

//Multi Monitor Display - Author Unknown

A0="1000 +flor&#40; sqr&#40; 48 &#41;48 &#41;",

Aspc=1,

srcX="x + 0.0025 * sqrt&#40; sin&#40; x * a0 &#41;+.983456789 &#41;",
srcY="y + 0.0025 * sqrt&#40; sin&#40; y * a0 &#41;+.983456789&#41;",

Vers=100

Would appreciate any help.

Regards BTT

sitsparky · Post by **sitsparky** » Tue Jun 07, 2011 3:32 pm

Hey BTT. You, jerohm, and others are much better at config writing than I, but I thought I'd chime in anyway. Could you maybe try "floor" rather than "flor". Our config programming page lists "flor" as deprecated, and maybe this is what's causing the error with the A0 variable.

http://www.soundspectrum.com/g-force/Do ... mming.html

Just a thought from a different kind of developer (ie. web).

JayPro · Post by **JayPro** » Tue Jun 07, 2011 4:59 pm

Y'all Prolly Know THis Already But...

A0 variables usually require require a randomization parameter (rnd function). This is not necessarily imperative, however.
In this case, you do need an operator of some kind after the second 48:
A0="1000 +flor( sqr( 48 ) + 48 )",

You can also write:
A0="1000+flor(rnd(48) + 48),
and
A0="1000+sqr(rnd(48) = 48)

@Sparky;
The deprecated functions like flor() and clip() ensure backwards compatibility, i.e. so that the GF 4.x> app can read configs from every prior version since the app's initial public release.
I chose GF 4 as my example since this is when they started introducing new components like Meta ratings, Vector-C based functionality and other things.

Post by **BTT** » Tue Jun 07, 2011 9:44 pm

Hello Sitsparky

Paul, you have given me more credit than I deserve. I am not a config writer of WaveShapes or FlowFields. My contribution to G-Force is by way of creating ColorMaps. Many thanks for your help and suggestion.

Hello JayPro

Yourself and Jerohm as authors of both WaveShapes and FlowFields deserve the credit. The following code has solved the problem with Multi Monitor Display:-

A0="1000 +flor( sqr( 48 ) + 48 )",

Thank you, much appreciated.

Regards BTT

sitsparky · Post by **sitsparky** » Wed Jun 08, 2011 4:00 pm

JayPro wrote:@Sparky;
The deprecated functions like flor() and clip() ensure backwards compatibility, i.e. so that the GF 4.x> app can read configs from every prior version since the app's initial public release.
I chose GF 4 as my example since this is when they started introducing new components like Meta ratings, Vector-C based functionality and other things.

Good to know. Thanks for the clarification. Though I do a lot of QA and support for SoundSpectrum products, my main duties are marketing and sales. I can "read" config files (for the most part), though I've never dared modifying or creating anew. I'll leave that to you more-than-able folks.