 | | What do these macros do?
|
|
I've been poking around with my NXT, and as usual I've decided to bite off more than I can chew. In trying to discover a way to *unset* pixels on the display without wiping the whole thing, I've been sifting through some of the less-discussed macros (...) (18 years ago, 11-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) YES jeff, you need to do your own firmare.. AND it needs to be a form of BASIC!!!!! :) Chris 10 ? clr 20 goto 10 (18 years ago, 11-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
Ok, well, replying to my own message in the best of internet style... I got impatient and starting prodding. After a few hard resets, I came up with the following: Yes, the Get/SetDisplayNormal() permits you to write directly to screen memory. This (...) (18 years ago, 11-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) Lots of very cool stuff deleted. Sorry I missed your original message, Jeff. You can write to both the Normal and Popup screen memory and toggle back and forth between which one gets displayed. This code flips between the two buffers for 10 (...) (18 years ago, 16-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) Thanks for your response, John. That tip about the dirty flag not being IOMAPpable is very, very useful; I could have wasted a lot of time working that out the hard way. I'm working on a graphical display widget to show a 'radar' (well, sonar) (...) (18 years ago, 21-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | RE: What do these macros do? [IOMAP Access Execution Times
|
|
(...) You're right. IOMapRead and IOMapWrite are very slow functions. They're slow because you pass a character string for the name of the module you want to access; the NXT-G firmware runs through the list of modules looking for a match on the (...) (18 years ago, 21-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) Is it possible to write in the display popup buffer? So that we can do double buffering? I made some quick tests, but it seems the drawing routines always write in the normal display buffer... Julien (18 years ago, 23-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) It is possible to write to the popup buffer but only by using the IOMap routine (SetDisplayPopup). The regular system calls which write to the LCD all write to the normal display memory. Unfortunately, as Dick Swan suggested, the current NXT (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: What do these macros do?
|
|
(...) John - if you've got someone's ear in this, could you also see if a GCC build of the firmware can be released? I know LEGO are unlikely to use GCC themselves as they can afford more specialised tools, but so far, I don't see much of a (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | compilation switch in BrickCC Command Center?
|
|
Thru brickcc command center, I wonder how to insert a user-defined compilation switch as I want to use it in the preprocessor directives. Input is greatly appreciated. --Elizabeth (18 years ago, 6-Feb-07, to lugnet.robotics.nxt, lugnet.robotics)
|
| |
| | Re: compilation switch in BrickCC Command Center?
|
|
(...) Are you talking about defining a macro via a command-line switch such as nqc -Susb -d -DMYVAL=xyz foobar.nqc or something of that sort? If that is what you have in mind then you can do it from within BricxCC with NQC but I have not yet (...) (18 years ago, 6-Feb-07, to lugnet.robotics.nxt, lugnet.robotics)
|
