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.

Sign up for GitHub

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

Jump to bottom

SF: SB: Better control over interactive mode #24

Open
iondev33 opened this issue Dec 21, 2023 · 0 comments
Open

SF: SB: Better control over interactive mode #24

iondev33 opened this issue Dec 21, 2023 · 0 comments
Assignees
@iondev33
Labels
bug Something isn't working
Milestone
ION 4.1.4

Comments

@iondev33
Copy link
Collaborator

The FSWLOGGER switch is used as an indicator to disable interactive mode in a number of utility and test programs; this seems wrong, as in crewed missions there will be flight software that might be operated by humans. A more narrowly targeted explicit switch, something like NON_INTERACTIVE, would be better. Also, when this switch is enabled we additionally need to #ifdef-out any functions that are exclusively invoked by the disable interactive code, e.g., handleQuit.
@iondev33 iondev33 added the bug Something isn't working label Dec 21, 2023
@iondev33 iondev33 added this to the ION 4.1.4 milestone Dec 21, 2023
@iondev33 iondev33 self-assigned this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iondev33 iondev33

Labels
bug Something isn't working
Projects
None yet
Milestone
ION 4.1.4
Development

No branches or pull requests
1 participant
@iondev33