> Try replacing the printf with fl_message. That will pop up a > dialog box. The > syntax is the same, so all you do is replace the text "printf" > with "fl_message". You will also need to include FL/fl_ask.H > (that is, if > you are using FLTK 1.1.x
Yes, that'll work. > I don't use Windows, but with KDevelop (Linux IDE), the > stdout is buffered. Under windows, it's not even buffered, it's just plain dropped... > The only way to be guaranteed that the printf's will appear is to use > fprintf(stderr, ...) I've had some success just by calling fflush(...) on KDEv. But I'm not a big IDE fan, so don't use it enough to say for sure. > or launch the app in a console. If you run a win32 app in a "DOS box" console, you still don't get the stdout, unless the app was specifically compiled with the "console" option (which prevents win32 from dropping the stdout.) The exception to that seems to be if you use an Msys shell rather than a DOS box as your console, in which case Msys seems *not* to drop stdio and it all works pretty much as you'd expect. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
