Subject:
|
Monitor() and Event()
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Mon, 23 Oct 2000 06:12:45 GMT
|
Viewed:
|
1914 times
|
| |
|
|
Can someone teach me more on Monitor() and Event()? Does the Monitor() check
the event status repeatly or we have to make a repeat task to activate the
monitoring job?
If it is not checking the event status repeatly, why we cannot just read the
input value to capture the status?
Camus Lai
|
|
Message has 3 Replies:
 | | Re: Monitor() and Event()
|
| (...) Monitoring is automatic (done by the firmware). Monitoring stops when control leaves the monitor statement, so something like this: while(true) { monitor(EVENTS) { } catch { } } will miss a lot of events. You need to configure the events using (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
| | | Re: Monitor() and Event()
|
| (...) The "monitor" control structure (as well as "acquire") is a very useful supplement of the existing control structures, such as "if", "while", "until", etc. Dave Baum already gave an example and with the following I also want to point out a (...) (24 years ago, 26-Oct-00, to lugnet.robotics.rcx.nqc)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
