Within thread tree context you have to take care not to hang it up with a dead-lock.
Usually you have to use the :start_queue to start threads.
Alternatively you may want to use
Use :start_cond, which is protect it with :start_mutex, to notify about running thread.
The following example creates a thread and does add an other thread to :start_queue. This causes it to be started as well. Note you want to access :start_queue using :start_mutex to avoid data races. But there is a convience function which does it for you.
Example 3.1. Starting threads
#include <glib.h> #include <glib-object.h> #include <ags/libags.h> AgsThread *main_loop; AgsThread *thread; AgsApplicationContext *application_context; application_context = ags_application_context_get_instance(); main_loop = ags_generic_main_loop_new(); ags_concurrency_provider_set_main_loop(AGS_CONCURRENCY_PROVIDER(application_context), main_loop); ags_thread_start(main_loop); thread = ags_thread_new(); ags_thread_add_child_extended(main_loop, thread, TRUE, TRUE); ags_thread_add_start_queue(main_loop, thread);
There many other functions not covered like mutex wrappers ags_thread_lock() and ags_thread_unlock(). As doing a closer look to the API there are functions to lock different parts of the tree. But all these functions should be carefully used, since you might run into a dead-lock.
To find a specific thread type use ags_thread_find(). You can use ags_thread_self() to retrieve your own running thread in case your using Advanced Gtk+ Sequencer thread wrapper.