I made the use of a separate thread optional in my
frontend, and if threads are used, widget opcodes
are rejected with an error. But they are enabled and
do work if the user turns off threading in the
preferences.
It is now also possible for the host application to
control the threading behavior of the widgets plugin
itself, disable the graphs or opcodes, or detect if
FLrun was called. See ChangeLog for more information.

On Tuesday 02 May 2006 00:07, Victor Lazzarini wrote:

> Well, FLTK will work, if coded properly, but
> not the widget opcodes, but as the GUI toolkit
> of the application itself. Then multithreading
> can be used, but then as prescribed by the FLTK
> model.
> 
> 
> Note that it is possible to make FLTK work more
> or less perfectly in all platforms. It's just a
> matter of avoiding multithreading.
> 
> For instance, the minimal Csound 5 GUI for OSX
> supports the FLTK widgets. But it's single-threaded