| | Re: NQC release
|
|
And that was the fix. Thanks for maintaining this code! (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
(...) It turns out one of the steps in the process I used to generate the .tgz source code archive not only got the wrong version from CVS but it changed all my unix-style line endings back to windows-style line endings. I've replaced the latest (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
(...) I'm apparently very confused. I could have sworn I checked the code here and there wasn't a "private:" before the class Chunk definition starting at line 81. But after double checking just now indeed there is one there. That's what had me (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
Ahh...I shouldn't add comments to anything before my first green tea of the morning. I moved line 56 back to public: and went to line 81 and found private: was already there... 81 private: 82 class Chunk 83 { 84 public: 85 86 const UByte* GetData() (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
(...) I was not sufficiently clear. My apologies. Line 56 needs to remain unchanged: public: Comments, by the way, in C++ are specified by '//' rather than '#'. I say that because it looks like your compiler is complaining about a line (56) that (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
Making progress: I changed the public: to private: in RCX_Image.h and here was the output after I did a `make clean`: [root@aluminum nqc-3.1.r1]# make g++ -o bin/mkdata -Inqc/ -Iplatform/ mkdata/mkdata.cpp nqc/SRecord.cpp bin/mkdata (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
(...) Can you try adding "private:" directly above the declaration of the nested type Chunk in RCX_Image.h? I'd like to confirm that that change fixes the problem. If any more compile errors (or warnings) show up let me know here or via email. (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: NQC release
|
|
Hi John! Thanks for the new release. On my Linux box I get a compile error. uname -a: Linux aluminum 2.6.10-1.770_FC3smp #1 SMP Thu Feb 24 14:20:06 EST 2005 i686 athlon i386 GNU/Linux [root@aluminum nqc-3.1.r1]# make g++ -o bin/mkdata -Inqc/ (...) (20 years ago, 16-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | NQC release
|
|
I've released a new version of NQC today (3.1r1). (URL) would be most grateful if a few non-Windows platform folks could download the source release and make sure it builds and functions correctly on your favorite platform. I *think* I fixed all the (...) (20 years ago, 15-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
(...) Heloooooooo? (Well, never mind I guess. Went back to the old firmware anyway 'coz this new one doesn't work.) Iain (20 years ago, 4-Mar-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
Hey Guys, Any ideas on that code, regarding that error no. 5? Iain (20 years ago, 11-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
(...) No no, don't be. It's my own stupidity/ignorance in progrmaming terms. I'm slowly learning. (...) Good stuff, John. Thank you for your work on this, it's unbeliveable. I got it to do what I need. Now, the only problem is it doesn't seem to (...) (20 years ago, 9-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Sending Commands to Spybot from RCX - Question from a Beginner to Comm area.
|
|
Hi Everybody, I have used SendSpybotMsg and SendSpybotCtrlMessage (of course in connection with resopective set messages) without any problems using BCC 3.3.7.5 and 3.3.7.9. These two commands gives RCX a nice control over spybot. Specially (...) (20 years ago, 8-Feb-05, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
(...) Application Programming Interface (URL) Oh my god. I'm completly lost :( Sorry. (...) I'm not sure what you are confused about. The API defines a series of values and functions which you can use in your NQC programs. The three lines above show (...) (20 years ago, 7-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
(...) Um. I have no idea what an API is :-/ (...) Oh my god. I'm completly lost :( (...) Whaaa?? (...) When I copy/paste that into BricxCC, I get an when I hit the Compile/download button: Undefined function: "SetUserDisplay"...?? I think I'm going (...) (20 years ago, 7-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
(...) Having downloaded a copy of swan_test.zip which contains the latest test release of BricxCC and NQC you can use nearly all the new and enhanced features in the Swan firmware. You can view the "official" API built into NQC by executing the (...) (20 years ago, 6-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
Okay, okay, bad form responding to my own post. I got the new firmware on my RCX, downloaded the latest version of BricxCC, and NQC. But I can't figure out how to use this SetUserDisplay command? I want to show a variable on the display. I have no (...) (20 years ago, 6-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Swan Firmware
|
|
(...) I feel so awful asking this, becuase I'm sure it must have been covered somewhere before - I'm not very good at understanding quite how everything works (API's and includes and so forth - no idea what that stuff is!). But here's my question: (...) (20 years ago, 6-Feb-05, to lugnet.robotics.rcx.nqc)
|
|
| | Re: Sending Commands to Spybot from RCX - Question from a Beginner to Comm area.
|
|
(...) First of all, my apologies for not answering you via email. I've been a bit busy at work. I needed to run some tests myself before I could properly respond as well. The 0x9223 from the RCX happens to match the IR sent out by the Spybot (...) (20 years ago, 28-Jan-05, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
|
| | BricxCC test release
|
|
Folks, I've been fiddling around with how BricxCC and NQC talk to the RCX when using the USB tower. It's because of several users experiencing problems when trying to download programs from within BricxCC (using NQC behind the scenes). Depending on (...) (20 years ago, 18-Jan-05, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|