Commit 3ca0a39f authored by John Ralls's avatar John Ralls

Bug 606378 - gdk doesn't handle non-main thread rendering on Quartz

Document that the restrictions on Win32 apply also to Quartz.
parent b8366027
...@@ -666,12 +666,12 @@ gdk_init (int *argc, char ***argv) ...@@ -666,12 +666,12 @@ gdk_init (int *argc, char ***argv)
* </informalexample> * </informalexample>
* *
* Unfortunately, all of the above documentation holds with the X11 * Unfortunately, all of the above documentation holds with the X11
* backend only. With the Win32 backend, GDK and GTK+ calls should not * backend only. With the Win32 or Quartz backends, GDK and GTK+ calls
* be attempted from multiple threads at all. Combining the GDK lock * must occur only in the main thread (see below). When using Python,
* with other locks such as the Python global interpreter lock can be * even on X11 combining the GDK lock with other locks such as the
* complicated. * Python global interpreter lock can be complicated.
* *
* For these reason, the threading support has been deprecated in * For these reasons, the threading support has been deprecated in
* GTK+ 3.6. Instead of calling GTK+ directly from multiple threads, * GTK+ 3.6. Instead of calling GTK+ directly from multiple threads,
* it is recommended to use g_idle_add(), g_main_context_invoke() * it is recommended to use g_idle_add(), g_main_context_invoke()
* and similar functions to make these calls from the main thread * and similar functions to make these calls from the main thread
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment