diff options
| author | Albrecht Schlosser <albrechts.fltk@online.de> | 2023-02-02 17:03:09 +0100 |
|---|---|---|
| committer | Albrecht Schlosser <albrechts.fltk@online.de> | 2023-02-02 17:09:14 +0100 |
| commit | 4e75549e7bd8b0ea032cf279066d0fac09577067 (patch) | |
| tree | d624dee7f9e58a9694328753f884cb6099324d7f /src/Fl_lock.cxx | |
| parent | fb00fb3d66d01613a1284090608db82424d83b0d (diff) | |
Update dependencies and fix whitespace errors
- replace tabs with spaces
- remove trailing whitespace
Diffstat (limited to 'src/Fl_lock.cxx')
| -rw-r--r-- | src/Fl_lock.cxx | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/Fl_lock.cxx b/src/Fl_lock.cxx index d7bdf9c34..117d047a5 100644 --- a/src/Fl_lock.cxx +++ b/src/Fl_lock.cxx @@ -179,10 +179,10 @@ int Fl::awake(Fl_Awake_Handler func, void *data) { argument will trigger event loop handling in the main thread. Since it is not possible to call Fl::flush() from a subsidiary thread, Fl::awake() is the best (and only, really) substitute. - + It's \e not necessary to wrap calls to any form of Fl::awake() by Fl::lock() and Fl::unlock(). Nevertheless, the early, single call to Fl::lock() used to initialize threading support is necessary. - + Function Fl::awake() in all its forms is typically called by worker threads, but it can be used safely by the main thread too, as a means to break the event loop. |
