On Monday 12 June 2006 17:57, Michael Gogins wrote:

> I have been building with noFLTKThreads=1, so I will change that and
> test csound5gui. I am sure I am linking with the fltk.dll because I
> get an error box if it's not in my PATH.

Did you also test CsoundVST without noFLTKThreads=1 ? I set the FLTK
flags to 274 (the same is used by csound5gui in multi-threaded
performance) in the 5.02.1 tagged sources, and that mode expects
noFLTKThreads=0. The difference between CsoundVST and csound5gui is
that the latter calls csoundCompile() from the main thread (where
Fl::wait() is called), while the former calls csoundCompile() from
the audio thread. It is csoundCompile() where the FLTK widgets are
created. With the flags set to 274, the widget opcodes never call
Fl::wait() (the host is expected to do that, which makes it especially
important to use a dynamic FLTK library), but they call Fl::lock()
and Fl::unlock() around many FLTK operations - probably not all places
where needed, though. If compiled with noFLTKThreads=1, Fl::lock() and
Fl::unlock() are never called, which (and possibly other effects of
noFLTKThreads) can interfere with the intended operation of
FLTK_Flags=274.


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net