Open main menu

Difference between revisions of "Windows/Console"

864 bytes added ,  11:56, 25 October 2010
Updated some arguments
m (cleanup)
(Updated some arguments)
Line 14: Line 14:


* Most Windows applications do not display a console window.
* Most Windows applications do not display a console window.
* Unknown games can be reported with a nice popup GUI window, and the game checksums in question can be exported to a file, which the user can copy and paste to a bug report
* Ideally, we could have a "Submit" button which the user can click on to submit unknown checksums
* Log files can be used instead of the console window, which can be erased every time ScummVM starts
* Sometimes, when ScummVM crashes unexpectedly, the program exits completely, and the user loses the error in question. This doesn't happen with a log file.
* Users need to restart ScummVM, to get more feedback, when bugs or issues occur and they haven't copied/pasted the relevant information from the console, and might not even be able to reproduce the bug/issue.


== Cons (Arguments Against Hiding The Console Window ==
== Cons (Arguments Against Hiding The Console Window ==
Line 20: Line 25:
* Many of the current warnings (i.e. loading related, missing code or features) in source code, can provide useful feedback 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.
* 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.
** 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. => Yes, but noone notices the console in this case anyway
* 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 overwritten, if a user relies solely on logs for reporting bugs or issues. This is exactly the same situation with console windows, though.
* A single log file can easily be over written, 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.
** 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.
* 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. '''I don't understand what this issue is about - Md5'''
* 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 behavior of GUI only programs, is to return the prompt straight away, if started by a command prompt.
* 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 behavior of GUI only programs, is to return the prompt straight away, if started by a command prompt. ''' This already happens with the currently submitted patch by m_kiewitz'''
1,502

edits