> > On Mar 4, 2007, at 5:17 AM, Nicholas Schwarz wrote: > > > I'm seeking some advice about how to use threads with FLTK, > > preferably without using FLTK's built-in lock and unlock features. > > What is it that you don't like about Fl::lock() and Fl::unlock()? >
I think that Fl::lock() and Fl::unlock() are very useful. The reason I don't want to use them is because I'll mostly be deploying this software on SuSE systems. The default install of FLTK on SuSE doesn't include thread support for some reason. Although it's not that big of a deal for me to re-build FLTK or to install a different rpm on my system, my users aren't computer programmers. They don't know how to compile things or what threads are. Also, they don't have administrator access to their computers. So, the less changes that have to be made to their systems the easier my life is in the long run. Thanks > > A thread that opens a socket will execute callbacks based on > > incoming messages. Those callbacks have to update widget values. Is > > it possible to make a message queue using FLTK's event handlers? I > > really don't like the idea of replacing Fl::run with a loop that > > polls a condition variable, but don't know of another way to do it. > > No need for that. At least under OS X and UNix, you can open a pipe > and make FLTK react to messages sent to that file handle by using > Fl::add_fd, etc. . But that is pretty much exactly what Fl::lock() > does for you anyways. > > ---- > http://robowerk.com/ > > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
