darby johnston wrote:
> Hi,
>
> I'm using FLTK 1.1.x for a couple of applications that have both a GUI and
> command line interface; this works great on UNIX, but not so well on Windows:
>
>> WIN32 applications without a console cannot write to stdout or stderr,
>> even if they are run from a console window. Any output is silently
>> thrown away.
>
> I think the options still get passed, but you can't print out a help screen
> or any error messages. Are there any way workarounds for this without having
> the application pop-up it's own console?
Did you try compiling your app as a console application? (eg. with
/subsystem:console)
That will allow you to open GUIs /and/ print to stdout/error.
If your app is invoked from a DOS window, that window will be used for
output.
If invoked from something other than a DOS window (eg. desktop shortcut),
then Windows will open a new DOS window for you, and your app's output
will be sent to that. The properties on the shortcut can be used
to make the new DOS Window hidden by default (stowed)
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
