Subject:
|
event driven vs. timing driven code...
|
Newsgroups:
|
lugnet.org.ca.rtltoronto
|
Date:
|
Fri, 17 Feb 2006 19:24:09 GMT
|
Viewed:
|
648 times
|
| |
|
|
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, and continue on its merry...
However, for this competition, I'm going (at least so far) on a pure event
driven code--do this until sensor is pressed, or do this until light value is
less than that...
I think in my entire code, I have one Wait command, and that's at the
beginning...
The problem arises, at least for me, is that I've never done it this way before.
I'm finding it difficult to account for the different events, and getting them
straight in my mind.
I think I've got a good grasp on it, but we'll see.
This is fun :)
Dave K
|
|
Message has 1 Reply:
 | | 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)
|
7 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
