incrementally-named arrays

[Bobo]

Not that I understand why you want to do this, but how about you start with telling MAXScript that 'v' IS an array?

v = #() --create an empty "master" array
i = 1 --set the index to 1
v[i] = #(1,2,3) --set the first sub-array of v to #(1,2,3)
...

Since you typed your code in global scope (bad idea, esp. when using single-character variable names which could be used by any other script), at a certain point you probably defined 'v' as array the first time you played with the idea and then v became a global variable for the duration of the session. The next day v wasn't defined and you ended up with errors.

So start like

(--open local scope
local v = #() --create an empty "master" array in LOCAL scope
local i = 1 --set the index to 1 in LOCAL scope
v[i] = #(1,2,3) --set the first sub-array of v to #(1,2,3)
...

)--end script and local scope

This will ensure that the variable v will exist only within the local scope of your current script and will not be visible to any other script. These variables will be "seen" by your rollout which is one scope deeper and can see any variables in higher scopes and the global one.

If you really want to have the array visible to anyone, you could make it global, but in that case it is advisable to use a VERY descriptive name to avoid collisions with other unrelated code:

(--open local scope
global BHNH_MasterArrayForIncrementalStuff = #() --this is your own unique name in global scope
local i = 1 --set the index to 1 in LOCAL scope
BHNH_MasterArrayForIncrementalStuff[i] = #(1,2,3) --set the first array
...

)--end script and local scope

[bhnh]

Great! Thanks, Bobo. I'm still inclined to overlook the global aspect of variables. It's a habit I've got to break.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.