 | | Re: The Datalog
|
| Sorry, Dean - now I got your point. There is indeed no way to read the contents of the datalog. What about storing the data (e.g. for path information, maps, etc.) into an ARRAY instead of the datalog? With RIS2.0 and the latest NQC version you have (...) (24 years ago, 10-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The Datalog
|
| (...) I think you answered your own question. :) (24 years ago, 10-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The Datalog
|
| (...) Lego has made it quite clear that they will not listen to us. They say that it pollutes their vision or something. All we can do is hope that the few people they do ask for feedback will point out these 'lacking' points. But, since version 2.0 (...) (24 years ago, 10-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The Datalog
|
| (...) I wouldn't be quite so pessimistic. Although TLG doesn't really participate in these conversations, I'm certain they are reading them. Also, several of the more annoying limitations of the original firmware were removed (or at least eased) (...) (24 years ago, 10-Oct-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: The Datalog
|
| (...) In that case: Dear Lego: Please allow random memory access via the next firmware, either through access to the datalog or some other mechanism. Thanks! (24 years ago, 10-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.dear-lego)
| | | | | Re: The Datalog
|
| (...) That's why my post ended on a positive note. It's not that I'm ungrateful. Without Lego I wouldn't have hundreds of thousands of bricks all over my house... heh heh. I also wouldn't have 3 RCX's, a Scout & a Micro Scout. Lego just moves very (...) (24 years ago, 11-Oct-00, to lugnet.robotics.rcx.nqc)
| |
