Creating Variables on-the-fly?

[momo_the_monster]

I'm writing code to toggle the (binary) state of buttonlights on a monome 40h, controllable by sending notes over my MIDI bus. I've attached my current code, it's pretty straightforward.

I set variable i to 0 (since our button starts 'off'). When a Midi Note is received, I run a function that checks the state of i - if it's 0, it should turn off the buttonlight (by sending the same MIDI note with a velocity of '0') and set i to 1 - it does the opposite if i is 1.

It works great until I add other buttons into the mix - because variable i is shared and does not always reflect the true state of the button I'm actually trying to affect.

Is there a way to dynamically generate a variable for each of these buttons? I've got a possible total of 64, and it seems like they should all have their own variable for holding state information. Thanks for any help you can give!

---

add_toggles.ck
Description:		Download (listen)
Filename:	add_toggles.ck
Filesize:	578 Bytes
Downloaded:	602 Time(s)

---

[Kassen]

[kijjaz]

i also have this one thing i wanna do:
being able to select a kind of oscillator to use before creating one.
(for example, a function that let the caller choose between SinOsc, TriOsc, .. etc)

i did something like this:

[moudi]

another possible solution with an array:

[Kassen]

Nice post! Good thinking and nice trick as well.

[momo_the_monster]

Excellent - thanks Kassen! Here's my original function:

fun void midi_toggle( int minote )
{
if (msg.data2==minote && msg.data3==127) {
minote => msg.data2;
if (i==0) { 127 => msg.data3; 1 => i; }
else { 0 => msg.data3; 0 => i; }
mout.send( msg );
}
}

I replaced the second if...else structure that tests for the state of the button with the bit you gave me - so now it looks like this:

fun void midi_toggle( int minote )
{
if (msg.data2==minote && msg.data3==127) {
minote => msg.data2;
!button_toggles[minote] => button_toggles[minote] => msg.data3;
mout.send( msg );
}
}

Of course I've previously declared button_toggles earlier with:
int button_toggles[64];

Thanks so much for the method! Like I said, this was my first try at programming in ChucK - I've felt the need to learn Max/MSP for a long time to build some interactive instruments that I haven't been able to do with Quartz Composer alone -- but I'm pretty sure I'll be able to use ChucK instead!

[Kassen]

[momo_the_monster]

Thanks for the suggestions - I wrote this program as a stopgap measure to provide me some needed functionality for the Monome 40h. The next iteration of official Monome programs should make this patch redundant, so I'm not planning to develop it further.

However, I am planning on creating a Simon-like call-and-repeat game using the Monome, and I'll certainly put your suggestions to use when I start up that project.

Thanks again!

[Kassen]

There's no need at all to defend this code; It's most definately not under attack. I myself make quick&dirty setups like that to test and prove concepts or to quickly get some temporary functionality all the time. It's very ChucKian.

You're doing great, looking forward to hearing about your game!