 | | 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)
|
