From a6dd0adac7078ea93955242ab4bad49c812c20a8 Mon Sep 17 00:00:00 2001 From: ManoloFLTK <41016272+ManoloFLTK@users.noreply.github.com> Date: Mon, 9 Jan 2023 15:07:46 +0100 Subject: Doc only: fix for "Fl::awake() and Fl::add_timeout()" (#524) --- documentation/src/advanced.dox | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'documentation/src') diff --git a/documentation/src/advanced.dox b/documentation/src/advanced.dox index 7e8b3ca4d..7489a4698 100644 --- a/documentation/src/advanced.dox +++ b/documentation/src/advanced.dox @@ -398,7 +398,9 @@ threads on all operating systems: of Fl::awake() mechanism and use that. (Intermixing calls to Fl::awake() should be safe with either however.) -\li Don't start or cancel timers from a worker thread +\li Starting with FLTK 1.4, it's possible to start (or cancel) a timer from a + worker thread under the condition that the call to Fl::add_timeout + (or Fl::remove_timeout) is wrapped in Fl::lock() and Fl::unlock(). \li Don't change window decorations or titles from a worker thread -- cgit v1.2.3