Changing a string and changing program flow are clearly analagous. Erm.
You said
"Maybe FDEV should force all ship systems except Life Support (for outposts) to shut down while docked, and activate only after clearance to launch has been granted? For instance, if I manually power off all modules except Life Support in my ship out in space or on the pad, none of them will do anything until I switch them back on (and I know it's obvious to practically everyone who will be reading this but the point is it's a straightforward safety implementation that can be toggled for all landing and docking statuses)."
So you're saying they should take the code they have with a bug and replace it with a completely different behaviour when your ship docks (which is conditional on where you've docked).
That's re-writing chunks of the docking code - maybe that's low risk and maybe not. You've not seen the code and neither have I. To suggest that the existence of a function the user can trigger through the GUI that seems to work means that the developer can call the same function for certain conditions and it will "solve the issue (and any future issues they haven't uncovered yet) permanently" is at best naive.
I'm not suggesting anything useful here because it's not a design issue that needs user feedback - it's a bug in the code that needs a developer who has sight of the source to assess and fix. Clearly guns shouldn't be firing in the outfitting screen, the fact that I can manually power off my thrusters in another part of the game has no bearing on that - you can't actually power off the hardpoints, only retract them, by the way, and deploying them so you can see what you're fitting is part of the outfitting screen functionality. So even your simplistic suggestion is flat out wrong.
You said
"Maybe FDEV should force all ship systems except Life Support (for outposts) to shut down while docked, and activate only after clearance to launch has been granted? For instance, if I manually power off all modules except Life Support in my ship out in space or on the pad, none of them will do anything until I switch them back on (and I know it's obvious to practically everyone who will be reading this but the point is it's a straightforward safety implementation that can be toggled for all landing and docking statuses)."
So you're saying they should take the code they have with a bug and replace it with a completely different behaviour when your ship docks (which is conditional on where you've docked).
That's re-writing chunks of the docking code - maybe that's low risk and maybe not. You've not seen the code and neither have I. To suggest that the existence of a function the user can trigger through the GUI that seems to work means that the developer can call the same function for certain conditions and it will "solve the issue (and any future issues they haven't uncovered yet) permanently" is at best naive.
I'm not suggesting anything useful here because it's not a design issue that needs user feedback - it's a bug in the code that needs a developer who has sight of the source to assess and fix. Clearly guns shouldn't be firing in the outfitting screen, the fact that I can manually power off my thrusters in another part of the game has no bearing on that - you can't actually power off the hardpoints, only retract them, by the way, and deploying them so you can see what you're fitting is part of the outfitting screen functionality. So even your simplistic suggestion is flat out wrong.