Subject:
|
Re: Program() always returns 0
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Mon, 6 May 2002 04:58:52 GMT
|
Viewed:
|
3931 times
|
| |
|
|
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:
int ud; // user display global
task main()
{
SetUserDisplay(ud, 0);
ud = Program();
}
Gus
|
|
Message has 1 Reply:
 | | Re: Program() always returns 0
|
| 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)
|
Message is in Reply To:
| | Program() always returns 0
|
| 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)
|
4 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
