 | | Re: global output control
|
|
"Matthew Miller" <mattdm@mattdm.org> wrote in message news:slrn8kshgc.sof.....bu.edu... (...) first, (...) It won't do any good to call Revert without Invert though... I guess one confusion with Revert is that it wouldn't switch the output back to (...) (24 years ago, 19-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
(...) The only problem is that "revert" implies that invert must be called first, and I don't think that is the case. (24 years ago, 19-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
"Matthew Miller" <mattdm@mattdm.org> wrote in message news:slrn8kpub3.v5a.....bu.edu... (...) "RevertOutput". (...) I think RevertOutput is fine. I actually wonder how often that call will end being used in user's programs? The InvertOutput command (...) (24 years ago, 19-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
(...) ObvertOutput? (24 years ago, 18-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | global output control
|
|
The Scout and RCX 2.0 both support what lego calls "global" control of the outputs. At first I thought the global calls somehow took precedence over normal calls, so I simply made global versions of all the output calls in NQC. However, after (...) (24 years ago, 18-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.x event processing
|
|
(...) <snip> Dave, Been out of town, and will look more at your messages this weekend. Thanks for the feedback. -- Gordon (24 years ago, 15-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.x event processing
|
|
(...) Getting things like Timer[0] = 100; to work while still allowing if (Timer(0) < 100) { } is a lot harder than I had anticipated, so I'm punting on array-style setting of the various RCX source (such as Timer(), UpperLimit(), etc). There are (...) (24 years ago, 13-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.x event processing
|
|
(...) Not really a stack problem, just a control flow issue. On suggestion for the event handling was something like this: begin_events(EVENT_MASK, event_handler); // put code that executes during event monitoring here end_events event_handler: // (...) (24 years ago, 10-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.x event processing
|
|
(...) #3, which was the approach you took. (...) I think what I liked about the approach in pBrick script was that it was fairly like coding a microcontroller in assembler: set up an interrupt vector and then include a label and code for the (...) (24 years ago, 5-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: communication brick <-> PC
|
|
(...) Cool. We'll wait patiently. :) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
|
