 | | main() not defined?
|
|
I get this error - "main() not defined" - when compiling. The code is copied straight from the Ferrari book. While C is the language of my choice, the line of code isn't so obtuse as to hide errors from me. So probably there is some other requisite (...) (23 years ago, 20-May-02, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
| |
| | Re: Program() always returns 0
|
|
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)
|
| |
| | Re: Program() always returns 0
|
|
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)
|
| |
| | 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)
|
| |
| | Re: NQC and BricxCC problem
|
|
John, The crash is because NQC is trying to print out an error message but doesn't have legitimate information about the lexical location (file, line number, etc) of where the error occurred. The error itself is from the "#pragma init" line - (...) (23 years ago, 5-May-02, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC and BricxCC problem
|
|
Dave (or anyone else who might have an idea), I'm trying to figure out a problem that a user reported regarding BricxCC and its interaction with NQC. (I've only tested it against the latest release of both BricxCC and NQC.) When attempting to (...) (23 years ago, 5-May-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Small bug in Bricxcc 3.3.4.5
|
|
hi John, thanks for the fast respons. After some invetsigation, I came to the conclusion that you are right, but I'm also right. (...) Yes this seems to work. But I'm not such a perfect programmer as you ;-) Now try to introduce an error and compile (...) (23 years ago, 22-Apr-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Small bug in Bricxcc 3.3.4.5
|
|
(...) I'm trying to duplicate what you describe and I'm unable to do so (in version 3.3.4.5). I started a new file. Pressed F9. Clicked on a template containing a "field". The template was inserted into the editor and the first (or only) field was (...) (23 years ago, 22-Apr-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Small bug in Bricxcc 3.3.4.5
|
|
hi John, I think there's a small bug in BricxCC version 3.3.4.5 (and also in some previous versions). When you insert a template it's not possible to type directly into the "fields". Instead you've to move the cursor 1 line up and then go with F10 (...) (23 years ago, 21-Apr-02, to lugnet.robotics.rcx.nqc)
|
