Subject:
|
Re: signals / legOS internals
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Sat, 26 Jun 1999 23:40:59 GMT
|
Viewed:
|
1413 times
|
| |
|
|
Lou Sortman <theball@bigfoot.com> wrote:
> Yes, that is it. A classic example is a full screen app such as vi.
> When being stopped, vi sets the terminal mode to something generic and
> saves any screen info that it needs. When resumed, it sets the terminal
> mode back to what it wants and redraws the screen. Now, obviously,
> running screen apps on the brick would be silly, but that is an example.
So is the idea that you might have a "shell" app that lets you control a
button or two and that takes over the lcd at times (say), and lets you
start, suspend, and stop other apps that control different, presumably
disjoint sets of motors and sensors, and with signals, when you suspend one
app, it can do something like shut down the motors and sensors it was
using, at least until it is resumed? That would make sense to some extent,
but is anybody really planning to run programs on the RCX this way? It
seems like overkill for such a small box with so little I/O, even more so
because it doesn't look like anybody is going to attempt to implement
dynamic linking and loading of new programs.
-Kekoa
|
|
Message is in Reply To:
 | | Re: signals / legOS internals
|
| (...) Yes, that is it. A classic example is a full screen app such as vi. When being stopped, vi sets the terminal mode to something generic and saves any screen info that it needs. When resumed, it sets the terminal mode back to what it wants and (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
32 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
