 | | RE: BricxCC release 3.3.2.12 —Marco Correia
|
| | | (...) I think that's a reasonable approach. If I send a .nqc source file to someone using a CyberMaster connected to a diferent COM port, then this is a better solution. Also, by sending a .nqc that usually goes to Program 5 on my RCX, it won't (...) (23 years ago, 29-Nov-01, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: BricxCC release 3.3.2.12 —Guido Heunen
|
| | | | | Hi John, I haven't installed the new version yet. Just a comment on my request. Your idea seems OK. However, this means you need two read two files. If I would have a look into my old.nqc file two months later I would see directly what settings (...) (23 years ago, 29-Nov-01, to lugnet.robotics.rcx.nqc)
|
| | | | | |
| | | | | | | Re: BricxCC release 3.3.2.12 —John Hansen
|
| | | | | | (...) I guess I don't see so close a tie between the NQC code in a .NQC file and the brick type, port number, and program slot. A program running on RCX in slot 3 downloaded via COM4 could just as well run on an RCX2 in slot 1 downloaded via USB2. (...) (23 years ago, 29-Nov-01, to lugnet.robotics.rcx.nqc)
|
| | | | | | |
| | | | | Re: BricxCC release 3.3.2.12 —John Hansen
|
| | | | (...) In the simplest implementation (i.e., the one I'm likely to write) if you double click on an NQC file it will always open a new instance of BricxCC. That's the way it works right now. I may have it always bypass the "search" form when opening (...) (23 years ago, 29-Nov-01, to lugnet.robotics.rcx.nqc)
|
| | | | |
