[Suggestion] Error feedback for command line usage on Windows #889
Replies: 5 comments
-
|
MessageBox in logE The reason why is console mode absent on Windows is because Furnace is built in the Windows subsystem, which prevents the appearance of a console when launched from the explorer, but also prevents command-line usage/console attachment. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to get these messages to show up on the command line for Windows users as well? |
Beta Was this translation helpful? Give feedback.
-
Console mode is present and works fine, except for the error/debug info logging into the command prompt. |
Beta Was this translation helpful? Give feedback.
-
I meant console output. Sorry for the lack of clarification. |
Beta Was this translation helpful? Give feedback.
-
|
Partially done! Furnace initialization failures (e.g. UI couldn't start, unable to load file, etc.) are now reported using MessageBox(). |
Beta Was this translation helpful? Give feedback.
-
I believe that users of most software should not have to constantly glance at the source code/documentation to be able to learn how to use it or know what they're doing incorrectly to be able to accomplish a certain task.
Furnace, in command line mode, does not do this at the moment (on Windows 10, anyway).
To help remedy this issue, I believe that Furnace should have some sort of error feedback upon a crash or user error (like JSIDPlay2 for example), and some sort of built-in command line documentation for the various command line parameters that Furnace currently has.
Another thing that I think may be needed is to show you when Furnace is running in the background (eg, playing a song in console mode), perhaps how JSIDPlay2 does it (it gives you some song stats and a runtime counter, and you can ctrl+c it in that state as well). This may also solve the issue that you have to do
taskkill /f /im furnace.exe(or your operating system's equivalent) to stop the music in command line mode, where it would be a lot easier to let the user kill Furnace by doingctrl+c.edit: After a quick glance at the source code, it appears that Furnace does indeed have some
printfs lying around for command line feedback, but these do not appear to print at all on Windows.Beta Was this translation helpful? Give feedback.
All reactions