| |
That would be great. Thanks Mark!
Obviously, it will be prudent to make some or all of these optional at
compile time... but I believe at least half of them are useful for most
users.
Anyone have an idea of priority on this addition? Should it be done now, or
added to the TODO list for a future release? Any idea of
usefulness/priority for the options given?
My 2 cents: Since some of these have already been written, the time
necessary to include them should be minimal. I will try to get what Mark
sends me into the code for testing (upon arrival).
Joe
(btw, remove spamblock. from email address when you send it)
"Mark Falco" <falcom@onebox.com> wrote in message
news:GtJvxC.E49@lugnet.com...
> > I have concidered adding a simple menu (using the view button or • something
> > in program.c perhaps) Could provide these functions:
>
>
> I created a user space program which does some of this. I call it • "inspector"
> as it mostly inspects the values of sensors. It also shows the current • battery
> reading and how long the RCX has been on. The UI is pretty simple to use. • It
> also allows you to select the type of sensor you have attached to each • port and
> then runs the values through the proper drivers. It's customized to use • my own
> user space drivers for third party sensors. If you are interested I can • e-mail
> it to you. Perhaps it would make a good starting point for what you • described.
>
> mark
|
|
Message is in Reply To:
 | | Re: Deleting Programs
|
| (...) I created a user space program which does some of this. I call it "inspector" as it mostly inspects the values of sensors. It also shows the current battery reading and how long the RCX has been on. The UI is pretty simple to use. It also (...) (23 years ago, 25-Mar-02, to lugnet.robotics.rcx.legos)
|
4 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
