 | | Re: event driven vs. timing driven code...
|
|
(...) When using events I tend to use a state model, and use the events to switch the state. So my main loop is: repeat forever if state 1 do stuff if state 2 do stuff if state 3 do stuff and then have eternal tasks defining the state. Works OK, but (...) (19 years ago, 19-Feb-06, to lugnet.org.ca.rtltoronto, FTX)
|
| |
| | Re: event driven vs. timing driven code...
|
|
(...) Welcome to MY world! thats how I have programed MOST of my bots, and THATS the number one thing that bites me in the A..... arm. you just CANT think of all the scenarios. This is going to be a GREAT game. (...) i am so impressed with your seek (...) (19 years ago, 18-Feb-06, to lugnet.org.ca.rtltoronto)
|
| |
| | event driven vs. timing driven code...
|
|
K, most of my codeing for every competition has been based mostly on timing--sure I had a few events, such as touch sensors and light sensors and such, but when touch sensors were pressed, the code was to back up for x seconds, rotate for x seconds, (...) (19 years ago, 17-Feb-06, to lugnet.org.ca.rtltoronto)
|
| |
| | Re: [rtlToronto] rtlToronto20 Poster Available
|
|
(...) Can't he just put them up at home? Steve ps very nice picture. (19 years ago, 17-Feb-06, to lugnet.org.ca.rtltoronto)
|
| |
| | Re: [rtlToronto] rtlToronto20 Poster Available
|
|
(...) They're up at my office and already people are talking about it. So your work is appreciated... Dave K (19 years ago, 17-Feb-06, to lugnet.org.ca.rtltoronto)
|
