 | | Monitor() and Event() —Camus Lai
|
| | | 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 (...) (24 years ago, 23-Oct-00, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: Monitor() and Event() —Dave Baum
|
| | | | | (...) 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() —Dave Baum
|
| | | | | (...) I decided to write a small sample program showing how to configure events. Check out events.nqc at (URL) reply to: dbaum at enteract dot com (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| | | | | |
| | | | | Re: Monitor() and Event() —Bernd Frassek
|
| | | | (...) 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)
|
| | | | |
