Extend advanced.dox multithreading to add additional caveats
about the use of show() and hide() from child threads, based on issues reported in fltk.general with tooltip windows causing issues. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@10476 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
parent
0fdb271a78
commit
596fd2784a
@ -82,7 +82,14 @@ threads on all operating systems:
|
|||||||
|
|
||||||
\li Don't \p show() or \p hide() anything that contains
|
\li Don't \p show() or \p hide() anything that contains
|
||||||
widgets derived from Fl_Window, including dialogs, file
|
widgets derived from Fl_Window, including dialogs, file
|
||||||
choosers, subwindows or those using Fl_Gl_Window.
|
choosers, subwindows or those using Fl_Gl_Window. Note that
|
||||||
|
this constraint may also apply to non-window widgets that
|
||||||
|
have tooltips, since the tooltip will contain a Fl_Window
|
||||||
|
object. In general, it is advised \b not to call \p show()
|
||||||
|
or \p hide() on any widget from the context of a
|
||||||
|
non-main thread (instead use the Fl_Awake_Handler function
|
||||||
|
variant of Fl::awake to have the main thread show or hide
|
||||||
|
the widget on behalf of the child thread.)
|
||||||
|
|
||||||
\li Don't call Fl::run(), Fl::wait(), Fl::flush() or any
|
\li Don't call Fl::run(), Fl::wait(), Fl::flush() or any
|
||||||
related methods that will handle system messages
|
related methods that will handle system messages
|
||||||
|
Loading…
Reference in New Issue
Block a user