(I don’t have a good title for this…)
But:
Null slots in an array stop being null when they should be in the inspector if I select the gameObject they are attached to.
I’ll take hints and suggestions on. I’m working in .js and I have some strange behaviour with (an??) array. I have a catch in a for loop that iterates through the array that says:
if (array[i] == null) {
DoSomething();
} else {
DoSomethingElse().
}
This works fine as long as I don’t have the game object selected in the inspector. If I select the game object I get a console full of null refs, as all the Null slots in the array get past the trap into the else part of the statement, but crap out as they are null, and don’t contain what the else DoSomethingElse is looking for.
o.0!
I’m not even sure what to post as an example…
This might all be moot, as it seems to work when built in the webplayer, but it still scares me.