 | | Re: Problems with BricxCC release 3.3.2.12
|
|
(...) Thanks for testing BricxCC, John. I appreciate it greatly. I'm glad it is working for at least some users. :-) John Hansen (23 years ago, 2-Dec-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Problems with BricxCC release 3.3.2.12
|
|
(...) Hi John: As you requested I just tried out your latest ver. 3.3.2.12. I have a P2 450, 256 megs of ram. A Radeon 7200, driver ver. 6.13.3276. My desktop is set at 1024 by 768. I just wrote a quick little program, downloaded to my RCX and ran (...) (23 years ago, 1-Dec-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Problems with BricxCC release 3.3.2.12
|
|
I've had reports of access violations and run time error 217 when trying to execute BricxCC version 3.3.2.12 (i.e., the most recently released version). It runs fine on my development machine but it exhibits this behavior on another PC in my house. (...) (23 years ago, 1-Dec-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.2.12
|
|
(...) 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
|
|
(...) 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)
|
| |
| | Re: BricxCC release 3.3.2.12
|
|
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
|
|
(...) 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)
|
| |
| | BricxCC release 3.3.2.12
|
|
I've uploaded release 3.3.2.12 of BricxCC. A previous release (3.3.2.11) implemented support for COM5 through COM8. Existing users that have saved a default USB port will have to re-establish their default if they upgrade to this release. In (...) (23 years ago, 28-Nov-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Bug report and enhancement request for BricxCC
|
|
Hi John, First of all, I want to tell you that I like to program in BricxCC. However, there are some minor things I would like to mention to you. There are four bugs (I think): When I click on the maximize icon the window got maximazed. But when I (...) (23 years ago, 28-Nov-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Now available: BricxCC 3.3.2.9
|
|
I've just uploaded a minor revision to BricxCC. Version 3.3.2.9 now correctly handles a few NQC compilation errors that it was not previously handling correctly. Specifically, there are a few (4) NQC errors that do not report line numbers (too many (...) (23 years ago, 19-Nov-01, to lugnet.robotics.rcx.nqc)
|
