Greg,

> On Apr 18, 2021, at 1:33 PM, Greg Ercolano <erco@seriss.com> wrote:
> 
> On 4/18/21 6:48 AM, Michael Sweet wrote:
> 
>> So honestly, the overhead of using threading locks, even for a single-threaded program, is so small that I would recommend that we make FLTK thread-safe by default.
> 
>     Right, that'd be great if possible.
> 
>     We just have to make sure that if FLTK starts with locks enabled, old apps calling Fl::lock()
>     before run() won't hang on the lock call.

My thought was that Fl::lock() and Fl::unlock() could be no-ops until Fl::run() is called.

________________________
Michael Sweet



-- 
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/ED212DBD-AEFA-4CA1-A1D1-461DD6E2505B%40gmail.com.