I set the configuration attribute windows-subsystem="windows" for Windows release builds to avoid having a terminal running alongside Sniffnet when opening the app by clicking on its icon.
However, this prevents users to see stderr and stdout even when launching the app from terminal; in case of errors, this doesn't allow to see a trace of the problem, making debug more difficult.
Additional context
A possible solution that comes to my mind is to redirect stdout and stderr to a new file in the app's configuration directory.
T-256
commented
1 month ago
Is there an existing issue for this?
What's the problem?
I set the configuration attribute
windows-subsystem="windows"for Windows release builds to avoid having a terminal running alongside Sniffnet when opening the app by clicking on its icon.However, this prevents users to see
stderrandstdouteven when launching the app from terminal; in case of errors, this doesn't allow to see a trace of the problem, making debug more difficult.Additional context
A possible solution that comes to my mind is to redirect
stdoutandstderrto a new file in the app's configuration directory.