You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
stderr
andstdout
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
andstderr
to a new file in the app's configuration directory.The text was updated successfully, but these errors were encountered: