![]() Better to use just "console", then the user can equally use "-console" and "-no-console" on the command line, as opposed to "-no-no-console" and "-no-console", respectively "-show-console" and "-no-show-console" :). There's another remark about the patch (and current SVN): neither "no_console" nor "show_console" strike me as good choices for the config key. No SCUMMVM folders in MY Ducuments folder please Please understand that I think that ScummVM is a really great application, and perhaps these things arent important for users on other OS-ses, but it would seem so logical to use the app dir for a config file. But I'll do some research on Windows pipes etc. Actually, this might be the best solution right now. Then, this whole teeing business reduces to inserting a few lines of code in our central console output functions (which would be used by warning, error, debug, etc.), making this rather trivial to implement. Of course, a very simple way to implement a tee on stdout is to use a wrappper app which invokes ScummVM, but that's not very nice, so I'd prefer to avoid it.Īnd on the long run, we should avoid *any* use of printf in our code. Plus, if we do that, we don't have to use FreeConsole at all, we can just hide the console. do a "tee"), but always creating a log file is important enough to warrant spending the extra effort. Of course it's a bit more work to redirect stdout/stderr to two destinations (i.e. With the console output redirected to log files in the %APPDATA%\ScummVM path (where available) or the current working directory (older Windows versions), when the '-no-console' option is used. The alternative patch uses FreeConsole(), which it is simpler, since the currently disabled method in ScummVM SVN offers no advantages. But offers a '-no-console' option, for users who would rather not have the console window around. I have attached an alternative patch, which still enables the console window by default in Windows, for feedback reasons. Unfortunately there doesn't seem to be any easy way to work around this problem, due to the way that console control is based on how Windows programs are compiled. Do not give access to host-os or host-etc - it will not be problematic but its bad practice if a programme doesnt need access to the full OS or config files, dont give it access. While compiling as GUI program means no feedback (to current console window) when using arguments, from a command prompt. Scroll down to the 'Filesystem' section and toggle access to either 'All user files' (your home folder) OR All system files (all files you can see except critical OS files). The problem with FreeConsle() is the prompt is not returned, when launched via a command prompt (in Windows 2000 onwards), unless the program in compiled as GUI program. ![]() Yes, the console Window is enabled in all Windows builds.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |