Issues with for loop?

[d.healey]

Is noteOnOffState a MIDI list?

[VirtualVirgin]

@d-healey said in Issues with for loop?:

Is noteOnOffState a MIDI list?

Not in this case, just an array.

[Lindon]

@VirtualVirgin try doing this instead:

function onController()
{
     Console.print(trace(noteOnOffState));

}

but it may well be that noteOnOffState isnt defined or visible to your call back.

[d.healey]

@VirtualVirgin said in Issues with for loop?:

Not in this case, just an array.

In that case instead of using 128 you can use noteOnOffState.length and then the loop will never exceed the number of elements in the array.

[VirtualVirgin]

@d-healey said in Issues with for loop?:

@VirtualVirgin said in Issues with for loop?:

Not in this case, just an array.

In that case instead of using 128 you can use noteOnOffState.length and then the loop will never exceed the number of elements in the array.

I just tried that while you were tying this, but I still get an error:

Here is the array declaration:

[d.healey]

@VirtualVirgin Don't use global, use const.

[VirtualVirgin]

@Lindon said in Issues with for loop?:

@VirtualVirgin try doing this instead:

function onController()
{
     Console.print(trace(noteOnOffState));

}

but it may well be that noteOnOffState isnt defined or visible to your call back.

I did use that earlier, but I don't know how to append it to use strings in between each returned index value.

[VirtualVirgin]

@d-healey said in Issues with for loop?:

@VirtualVirgin Don't use global, use const.

Well somehow it works now once I added the
i + ": "
to the print command.

I didn't change the variable type yet.

const variable will be available across the different callback scripts?

[d.healey]

@VirtualVirgin A const will be available throughout the MIDI processor in which it is declared. It won't be accessible from other MIDI processors.

[d.healey]

@VirtualVirgin It's still saying undefined for that variable. You haven't solved the problem.

Where are you populating the array?

[VirtualVirgin]

@d-healey said in Issues with for loop?:

@VirtualVirgin A const will be available throughout the MIDI processor in which it is declared. It won't be accessible from other MIDI processors.

And does the scope of a global include the other MIDI processors (out of curiosity)?

[d.healey]

@VirtualVirgin said in Issues with for loop?:

And does the scope of a global include the other MIDI processors (out of curiosity)?

Yes, but there is usually a better method. Global variables lead to less modular code, which is more difficult to maintain and debug. I have yet to use them in any project.

[VirtualVirgin]

@d-healey said in Issues with for loop?:

@VirtualVirgin It's still saying undefined for that variable. You haven't solved the problem.

Where are you populating the array?

No, no! It is working properly.
Those "undefined" indexes are not written to yet.
Only those which have been written to have a value (1 or 0 here).

If you see, index 60 has a value of 1, meaning that middle C has note on.

If it matters later, I could initialize the array with all 0s, but I don't know that I need that data yet.

[d.healey]

@VirtualVirgin said in Issues with for loop?:

Those "undefined" indexes are not written to yet.

The error you created this thread for is caused by the values being undefined

In this situation you need to filter out undefined values, this can be done with a simple if inside the loop.

if (!isDefined(noteOnOffState[i])
    continue;

If you're just storing a 1 or 0 in the array then you should probably use a MIDI list.

[VirtualVirgin]

@d-healey said in Issues with for loop?:

@VirtualVirgin said in Issues with for loop?:

Those "undefined" indexes are not written to yet.

The error you created this thread for is caused by the values being undefined

In this situation you need to filter out undefined values, this can be done with a simple if inside the loop.

if (!isDefined(noteOnOffState[i])
    continue;

If you're just storing a 1 or 0 in the array then you should probably use a MIDI list.

That error was coming up for trying to print from the loop.
That error disappeared when I added
i + ": "
to the Console.print()

The console is printing the loop and the error is no longer in the console.

[VirtualVirgin]

Without
i + ": " +

With

[d.healey]

The error is telling you that the thing you are trying to print is undefined. When you add i + ": " + then you are no longer printing something that is entirely undefined. - However as you can see from the console output the array part of it is still undefined.

[Oli Ullmann]

@VirtualVirgin
If you do not want to initialize your array with 0 or 1, you could also initialize it with -1.

[VirtualVirgin]

@d-healey said in Issues with for loop?:

The error is telling you that the thing you are trying to print is undefined. When you add i + ": " + then you are no longer printing something that is entirely undefined. - However as you can see from the console output the array part of it is still undefined.

Right, but the
[i]
is the original source of the error

If the array is populated with anything, then it has a length
so that variable should not be undefined.

The "undefined" that is now printing from those indexes are different "undefined" because they are are saying that that particular index is undefined (not written to).

The "undefined" referred to in the original error returns how many indexes are written to, which in essence was saying "0", which was incorrect.

[Oli Ullmann]

@VirtualVirgin
You probably fill your array according to the note numbers. So 60 for C3. If you now press C3, array element 60 is filled and the array has a length of 61, which means that elements 0 to 59 remain undefined. This is probably where the error comes from. It therefore makes sense to initialize the array with initial values.