 | | Re: RIS 2.0 or 1.5 (minimum requirements)
|
|
A more important consideration is whether USB or Serial is more convenient on your notebook. 1.5 comes with a COM port interface, and the 2.0 comes with a USB interface. USB is a lot better, if you have it. (...) (23 years ago, 20-Mar-02, to lugnet.robotics.rcx.nqc)
|
| |
| | RIS 2.0 or 1.5 (minimum requirements)
|
|
I am going to buy the RIS 2.0, but I am not quite sure if I should better buy the RIS 1.5. That is, because my notebook (366 Mhz PII, 64 MB RAM, but only 2.5 MB Video RAM) does not fully meet the minimum requirements as stated by LEGO (what is (...) (23 years ago, 20-Mar-02, to lugnet.robotics.rcx.nqc)
|
| |
| | BricxCC release 3.3.4.4
|
|
I've released BricxCC version 3.3.4.4. It fixes a timeout problem when trying to find the Cybermaster brick (although not all users experienced this problem). It also fixes some problems on the Color tab of the Preferences dialog. It fixes the (...) (23 years ago, 19-Mar-02, to lugnet.robotics.rcx.nqc)
|
| |
| | New version of NQCEdit
|
|
Version 1.6 of NQCEdit is now released. This program is a front-end IDE for the NQC command line compiler that offers syntax coloring. NQCEdit is able to do most of the things that NQC is capable of: - Compile program for all targets - Download (...) (23 years ago, 10-Mar-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
(...) It looks like the "slowness on shutdown" that I was experiencing when I closed BricxCC while multiple editor windows were open was causing access violations on your machine. What was happening was the code explorer would kick off a thread to (...) (23 years ago, 26-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
hi John, getting the latest video driver (Geforce 2MX, driver DetonatorXP v23.11) didn't help :-(, but .... you're new version 3.3.3.9 DID help :-) So thanks again ! I can't see any relevant changes from your "enhancements" list, but maybe you (...) (23 years ago, 26-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | BricxCC release 3.3.3.9
|
|
I've released another version of BricxCC (3.3.3.9). In this release: 1) Fixes to Cybermaster-specific items on the Watch window and graph 2) Fixed slow shutdown caused by Code Explorer 3) Added hints on Code Explorer preferences dialog to help (...) (23 years ago, 25-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
(...) I'm afraid this may have something to do with Win98 and ImageLists. It sounds like it might be a video driver bug as well. Make sure you have the very latest driver for your video card. I'm debating about going back to using bitmaps rather (...) (23 years ago, 22-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
hi John, >>To day I had an even stranger experiences: > 5. Use Explorer to search your computer for *.dsk files and delete any that > are obviously NQC-related (they will have the same file name as your .NQC > files except with the .DSK extension). (...) (23 years ago, 21-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
(...) Try this. 1. Delete the BricxCC key from the Registry (HKCU/Software/BricxCC). 2. Run BricxCC and bring up the Preferences dialog. 3. Make sure the "Autosave Options/Project Desktop" checkbox is NOT checked. 4. Close BricxCC. 5. Use Explorer (...) (23 years ago, 21-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Communication between 2 Robots - Movement transmition
|
|
Hi! I am a new member of your community, and i would like to ask the following question. Please excuse me if something similar has been already posted in the past, but i performed a seach in the previous posts and i did not found any answer to my (...) (23 years ago, 21-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: maximum number of variables in RCX2 ?
|
|
(...) Lego's usage of the terms'local' and 'global' is a little different than what most people expect. In the RCX, global storage is available across all tasks while local storage is avaialble per task. This is different from the more traditional (...) (23 years ago, 21-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: maximum number of variables in RCX2 ?
|
|
(...) Remember that the RCX has no stack or heap. This means that, effectively, there is no memory pool from which to allocate things. Here, 'local' means belonging to the current task not the current function, and the number of tasks is fixed (at (...) (23 years ago, 20-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: maximum number of variables in RCX2 ?
|
|
Hi John, (...) Yes ! Using more tasks you will get more local space (for each task 16). So maximum number of variables is 32+(16*10) = 192 (...) That's how NQC is handling memory for local variables in functions, subroutines, tasks. Local has a (...) (23 years ago, 20-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: maximum number of variables in RCX2 ?
|
|
(...) this (...) only (...) variables (...) the (...) From my understanding of NQC, the compiler automatically selects the most suitable location to store variables. Global variables are obviously always allocated in one of the 32 global storage (...) (23 years ago, 20-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | maximum number of variables in RCX2 ?
|
|
When using the RCX2 target, the NQC manual (Section 2.2.4) states that 32 global variables, and 16 local variables (per task) are allowed. Does this mean that the whole program can only have 48 variables total when using only one task, ie. "main" , (...) (23 years ago, 20-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
John Hansen wrote: > In lugnet.robotics.rcx.nqc, Stef Mientki writes: > >>I know the cause, you know the solution ;-) >> >>The size of BricxCC when opening the first file, depends on the SIZE of >>the file to be opened. >> 8 bytes, window stays as (...) (23 years ago, 19-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
(...) Yes that's exactly what I'm trying to say !! To day I had an even stranger experiences: 1. the size of BricxCC became smaller after opening the first file, still depending on the size (or is it the content) of the file 2. in one of the tests I (...) (23 years ago, 19-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
(...) Well, I'm stumped. I cannot get the behavior you describe to occur no matter how hard I try. I'm not sure what you mean by "I know the cause, you know the solution". Have I understood your description of the problem correctly? Are you saying (...) (23 years ago, 19-Feb-02, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: BricxCC release 3.3.3.8
|
|
hi John, thanks for your attention. I know the cause, you know the solution ;-) The size of BricxCC when opening the first file, depends on the SIZE of the file to be opened. 8 bytes, window stays as it is 256 bytes, blows the window up to about (...) (23 years ago, 18-Feb-02, to lugnet.robotics.rcx.nqc)
|
