 | | Re: global output control
|
|
(...) It's a perfectly good word! (It's not in M-W, but OED has it. And M-W has "obverse"....) :) And, it describes exactly what you want. (24 years ago, 20-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
(...) I was thinking of RestoreOutput myself, but then I was wondering if it implied restoring the enable/disable state as well. I'd like to keep the calls 'paired' as much as possible... EnableOutput / DisableOutput InvertOutput / ???Output I know (...) (24 years ago, 20-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
Just had to add my two cents worth; NegateOutput RestoreOutput JB (24 years ago, 20-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
(...) What's wrong with Obvert? (24 years ago, 20-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: global output control
|
|
(...) How about DontInvertOutput? Not beautiful, but IMHO clearer. Jürgen (24 years ago, 20-Jun-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
