UIUC85

18th October 2003 23:02 UTC

Wish
1 word... arrays.
lol that would kick ass

UnConeD

19th October 2003 05:13 UTC

IMO mostly only useful if coupled with a looping construct :). Except for maybe stuff like a scope with an array entry per point (because a scope is just a loop).

dirkdeftly

19th October 2003 06:28 UTC

i know it'd make my life a whole lot fucking easier.

btw, why is there a variable limit in the first place? would it have to be applied to an array construct object by object, or by each array? if it's for memory purposes, then a way to manually set the number of variables supported would be extremely useful...

UIUC85

19th October 2003 08:56 UTC

Yeah I was thinking of the same thing unconed. Create arrays that correspond with the SSC's... And adding a for loop command isn't a bad idea either eh? I think the interface in the SSC could be adjusted a bit too. He could throw all those variable and command listings into one button and then make it more like the dynamic movement interface with the scrolling text areas. Keeping all those variables in one line is really hard to read, especially if a for loop were ever added... Yikes! That would be ugly...

You know another good idea would be to add two variables to the DMs that would contain the value of the current X and Y grid values. So if you had a 32x32 grid then you'd get values between 1-32 for both. Just a thought.

UnConeD

19th October 2003 21:25 UTC

UIUC85: I think you need to try out AVS2.7pre if you're complaining about the superscope interface.


AFAIK DM gridvars goes, you can calculate that yourself:

Frame:
gx=0;gy=0;
lx=-2; // keep track of last x

Point:
.. (code goes here)

gx=gx+1;
newline=below(x,lx);
gx=if(newline,0,gx);
gy=if(newline,gy+1,gy);
lx=x;

Should work for any gridsize (might contain bugs, quickly typing this up).