Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it so incoming telemetry data doesn’t interrupt the current prompt #8

Open
GrahamDrive opened this issue Feb 1, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@GrahamDrive
Copy link
Member

Improvement: Make it so incoming telemetry data doesn’t interrupt the current prompt

Currently, any incoming telemetry gets written to the console, right after the current prompt. If you’re in the middle of writing a prompt, it will be split in two by the telemetry data. We would like to insert the telemetry data right before the current prompt, as opposed to within it.

@GrahamDrive GrahamDrive added the enhancement New feature or request label Feb 1, 2024
@GrahamDrive GrahamDrive transferred this issue from UMSATS/cdh-tsat Feb 1, 2024
@DaighB
Copy link
Contributor

DaighB commented Feb 13, 2024

This issue similarly occurs for any print statements not within the command line interface class, due to the parallel nature of SOTI. Looking into the Python ‘curses’ module could be an option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants