Re: Problems with the "mwindows" switch

[sbelmont700@gmail.com]

On Friday, May 22, 2015 at 2:35:59 PM UTC-4, NiGHTS wrote:
> 
> Any hints on what could be wrong is be highly appreciated!
> 

A Win32 executable is either 'console' or 'windows' (CUI or GUI).  This is, effectively, what the -mwindows switch controls, with its omission indicating CUI.

Essentially, a CUI executable gets its standard output handle from its parent console; so if you spawn a CUI from the shell, it uses the same console for output, and you get it in the same window as the shell.  Not so with a GUI app, that has no default output, and would open a new window should you try (via AllocConsole()).

So, if you use the -mwindows switch, you get no default console and your text goes nowhere.  If you remove it, you will always get a console whether you want it or not.  There is, officially, no way to create a windows executable that is dynamically both.

There is probably a more subtle reason as to why your GUI doesn't appear when -mwindows is present.


(http://blogs.msdn.com/b/oldnewthing/archive/2009/01/01/9259142.aspx)


-sb