Subject:
|
Re: Extending the firmware through DrawGraphic()
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Wed, 21 Feb 2007 16:24:54 GMT
|
Viewed:
|
13390 times
|
| |
|
|
In lugnet.robotics.nxt, John Hansen wrote:
> An RIC file is a graphic program. It contains a series of drawing opcodes.
> When you call the DrawGraphic system call it executes all of the opcodes in the
> RIC file in sequence. Trying to jury-rig that file format to let you only
> execute a subset of the drawing commands inside the RIC does not sound like a
> good idea to me.
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 would obviously be a big advantage.
Thanks (and Philo)
Jason R
|
|
Message is in Reply To:
 | | 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 (...) (18 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
7 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
