TrustedUser
574
edits
Difference between revisions of "Windows/Console"
Jump to navigation
Jump to search
Added Kirben's Cons Arguments
(Created Basic Framework for "Windows/Console" Page) |
(Added Kirben's Cons Arguments) |
||
| Line 16: | Line 16: | ||
* Most Windows applications do not display a console window. | * Most Windows applications do not display a console window. | ||
== Cons (Arguments | == Cons (Arguments Against Hiding The Console Window == | ||
* | * How do we report unknown games, or games with missing files to users? | ||
* Many of the current warnings (i.e. loading related, missing code or features) in source code, can provide useful feedback to users. | |||
* If a known issue occurs, but isn't suitable for GUI feedback, then users lose that information. | |||
For example: Original bugs in games based of AGOS game engine, can cause a few wait timeouts, which can make ScummVM appear as locked up. | |||
* Users need to restart ScummVM, to get more feedback, when bugs or issues, and might not even be able to reproduce the bug/issue. | |||
* A single log file can easily be over writen, if a user relies solely on logs for reporting bugs or issues. | |||
** Multiple logs would lead to more confusion, about which file to submit, if that method was used. | |||
* If a toggle is added for opening/closing the console window (showing all previous output), users will be dumped back to the desktop. And jumping back into ScummVM can result in further issues, of screen going out of sync or crash, with poor display drivers. | |||
* The current option is inconsistent, when starting directly (no console), compared to starting via a command prompt (console used, and prompt not returned). The standard behaviour of GUI only programs, is to return the prompt straight away, if started by a command prompt. | |||