Thanks for the suggestions... Greg Ercolano wrote:
> Did you try compiling your app as a console application? (eg. with > /subsystem:console) I believe so; I'm currently using cmake which has a WIN32 option for executables, and I assume that's what it's doing. > 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. But there's no way to keep Windows from opening a new console while still letting it use an existing one? > The properties on the shortcut can be used to make the new DOS Window > hidden by default (stowed) Interesting, I'll check that out. imm wrote: > Very much in the "workarounds" department... If you invoke your apps > from an Msys shell (part of mingw) rather than from a DOS box, then > stdout/stderr are *not* dropped, and it behaves much as a unix shell > does. But that's probably not all that useful to you, I'd guess. Msys is great, I do all my Window development with it; but I'm not sure the users would like it so much. Thanks, Darby _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
