On 20.12.2010, at 19:28, John Hoare wrote: > I am the author of a simple robot control software library. Under normal > operation, a graphical window will only show up if users request to display > an image taken by the robot's camera. > > Right now, I have the drawing being handled by a separate thread, which does > all the FLTK calls. This thread is constantly calling Fl::wait(). > However, although this seems to work fine on Linux and OS X, it does not seem > to work at all on windows (under cygwin)
MSWindows does not allow any GUI calls from threads other than the main thread. You either need to move all GUI calls into the main thread, or use timeouts instead of threads to do your calculations. This is a limitation of MSWindows. > Is there an example of an fltk program that does not always have a window > open, and exists beyond that of the fltk window's life. (All the examples > seem to end once the window is closed.) Yes. Fluid has acommand line mode in which it merely converst .fl into .cxx files with no GUI at all. As long as you don't call Fl_Window->show(), no UI will be generated. Once you close all windows, Fl::run() will return, but you can call somethign->show() and Fl::run() again at any time. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
