wally_z:
I appreciate the reply, but this doesn't really help me at all. I would rather use delay(), and if I try to use "for()" it just loops until it reaches the certain integer that it is supposed to stop at.
If you insist on using delays, then you'll have to liter your code if a bunch of selection statements checking for a state change (implemented through interrupts). That would be a pretty poor way to implement it, though. Another option is to tie the button to reset, and store the state change in EEPROM. On startup, it pulls the data from memory, increments it, and goes into the loop. That method would work if you plan on doing nothing else with the micro.
I'm not sure what you mean by the for() loops. Yes that's what it does, why is that a problem?