| Commit message (Collapse) | Author | Age |
|
|
|
| |
Signed-off-by: Mike Beattie <mike@ethernal.org>
|
|
|
|
|
|
| |
AltosLink is the class providing the 'run' method, after all...
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
Deal with missing data by checking for MISSING in more places.
Handle serial communication failures during send by reporting back
from libaltos.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
instead of having it in altosui
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
This moves some of the logic for managing when to present the 'cancel'
dialog for remote operations to altoslib.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
AltosLink owns all of the device configuration, so remove that from
AltosSerial and make sure that AltosLink provides the right function
signatures (wasn't using the new direct frequency setting command).
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
No sense having them live deep in the file system.
Signed-off-by: Keith Packard <keithp@keithp.com>
|