DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2580 Version: 1.3-current (somehow that last response posted while I was editing it..) ..there are cases where an app may need to run in an 'unattended' manner that doesn't interact with the window manager (eg. -help, or pure command line only operations). Matt described an example in fltk.development where fluid is run in a purely command line context via Makefiles to generate code; FLTK should be able to build on headless machines or via ssh connections without interacting with the wm. Maybe instead have the FLTK code (Fl::wait()?) check if the display has been opened first, and either return immediately or call the Fl::error() error handler to print a descriptive message about the display not being initialized yet. Link: http://www.fltk.org/str.php?L2580 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
