[Qt-interest] stdout of MSWin GUI application run from console

[Graeme Gill]

Rainer Wiesenfarth wrote:
> To me, this would make _two_ applications, probably sharing a large
> amount of code.

It depends on the nature of the application. For my type of applications,
the console I/O is very useful for command line options, usage etc.,
+ debugging.

> A _GUI_ application should use the GUI only, without the need of an
> attached console. If started by a console, it should ideally detach from
> it rather than polluting the console with random garbage output (like
> e.g. kate does on Linux). In any case, it must not rely on the presence
> of a console.

When I'm building cross platform applications I'd like as much
uniformity as possible, and it's MSWin that's the odd one
out here, having "GUI" and "console" modes. So something that
make MSWin applications more similar to the other platforms
is a very good thing in my book.

> A _console_ application however must not use the GUI at all. That is, it
> should also run in a SSH session without requesting a display.

Depends on the application. I have a set of console applications
that have to be able to put up windows for graphical tests.
So you can't assume one way or the other.

> ... and back to the thread's subject: (MS) Windows GUI applications do
> not use a console, fullstop. If you want Linux behavior, run Linux... ;-)

Sorry, and here's me thinking that Qt is a cross platform library...

Graeme Gill.