 | | Program() always returns 0 —Brian B. Alano
|
| | | The following code always displays 0 regardless of the program slot in which it is run. Is this a bug, or do I not understand the purpose of Program()? I'm using the 2.0 firmware and NQC 2.4 r2. task main() { SetUserDisplay(Program(),0); (...) (23 years ago, 6-May-02, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: Program() always returns 0 —Gus Jansson
|
| | | | | SetUserDisplay does not work like that. You need to specify either a sensor, timer, or global variable. Once you have done that it will continuously update the display as the value changes. In your case you should write your program something like: (...) (23 years ago, 6-May-02, to lugnet.robotics.rcx.nqc)
|
| | | | | |
| | | | | | | Re: Program() always returns 0 —Dave Baum
|
| | | | | | I believe any data source (not just timers/sensors/variables) can be used in SetUserDisplay. The big limitation is that local variables cannot be used since the display is updated in a global context independent of the tasks. If you know of data (...) (23 years ago, 8-May-02, to lugnet.robotics.rcx.nqc)
|
| | | | | | |
| | | | | Re: Program() always returns 0 —Dave Baum
|
| | | | Oops. Looks like a bug in the NQC API file. I just fixed the bug in the NQC source, but it's not major enough to warrant a new release yet. In the meantime, you can add the following lines to the top of of your source file as a work-around: #undef (...) (23 years ago, 8-May-02, to lugnet.robotics.rcx.nqc)
|
| | | | |
