Menu
▾
▴
#80 Better control over interactive mode
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.
Discussion
Anonymous
This needs to be handled very carefully, as it could screw up existing flight software accommodations. Also, it will affect a large number of programs. Since it doesn't seem to be an urgent problem, I'm slipping it to the 3.5.0 release.
Not urgent, slipped to version 3.5.1.
Still not urgent. Slipping it to version 3.6.1.
Still not urgent, slipping to 3.6.3.
Still not urgent, slipping to sometime in 2020.
Still not urgent, slipping to sometime in 2021.
Closing for now. This is tracked under GitHub and will not be address in the near term. We want to better understand the requirements before adding features. The actual human-flight configuration may be simpler or more complex, depending on the human interface design. So we will not commit resource until we are clear. But this is important.