 | | Re: Extending the firmware through DrawGraphic()
|
|
(...) Yikes - I had no idea it was that convoluted! I want to put on some new graphics functions but I think I'll devise my own file format for those. I'll see if it's possible to hijack DrawGraphic to test it at least, but supporting new opcodes (...) (19 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Extending the firmware through DrawGraphic()
|
|
(...) These variables do get used by the existing RIC format. I could tell you what they mean but then I'd have to kill you. :-) It definitely is not a good idea to try to use them for something completely different. It seems better to just add a (...) (19 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Extending the firmware through DrawGraphic()
|
|
Hello Jason, (...) There was a paper about RIC on NXTasy a few days ago: (URL) (19 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Extending the firmware through DrawGraphic()
|
|
Having made an earlier suggestion about using file names to extend the capabilities, I've looked into it a little further and found something very useful. The 'NXTDrawPicture', or 'DrawGraphic' command can take an arbitrary array of variables. The (...) (19 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Improving the firmware?
|
|
(...) It's a good plan, but I don't think that's the right command. If someone was calculating the position of a line to draw it may well start or end off-screen in the negative values. How about hijacking the FileOpen command, and apply URL-type (...) (19 years ago, 20-Feb-07, to lugnet.robotics.nxt)
|
