GLib.MainContext¶
record (struct)
The GMainContext struct is an opaque data
type representing a set of sources to be handled in a main loop.
Constructors¶
new¶
Creates a new MainContext structure.
new_with_flags¶
Creates a new MainContext structure.
Parameters:
flags— a bitwise-OR combination of flags that can only be set at creation time
Methods¶
acquire¶
Tries to become the owner of the specified context.
If some other thread is the owner of the context,
returns false immediately. Ownership is properly
recursive: the owner can require ownership again
and will release ownership when MainContext.release
is called as many times as MainContext.acquire.
You must be the owner of a context before you
can call MainContext.prepare, MainContext.query,
MainContext.check, MainContext.dispatch,
MainContext.release.
Since 2.76 context can be NULL to use the global-default
main context.
add_poll¶
Adds a file descriptor to the set of file descriptors polled for this context.
This will very seldom be used directly. Instead
a typical event source will use g_source_add_unix_fd() instead.
Parameters:
fd— aPollFDstructure holding information about a file descriptor to watch.priority— the priority for this file descriptor which should be the same as the priority used forSource.attachto ensure that the file descriptor is polled whenever the results may be needed.
check¶
Passes the results of polling back to the main loop.
You should be
careful to pass fds and its length n_fds as received from
MainContext.query, as this functions relies on assumptions
on how fds is filled.
You must have successfully acquired the context with
MainContext.acquire before you may call this function.
Since 2.76 context can be NULL to use the global-default
main context.
Parameters:
max_priority— the maximum numerical priority of sources to checkfds— array ofPollFDs that was passed to the last call toMainContext.query
dispatch¶
Dispatches all pending sources.
You must have successfully acquired the context with
MainContext.acquire before you may call this function.
Since 2.76 context can be NULL to use the global-default
main context.
find_source_by_funcs_user_data¶
def find_source_by_funcs_user_data(self, funcs: SourceFuncs, user_data: int | None = ...) -> Source | None
Finds a source with the given source functions and user data.
If multiple sources exist with the same source function and user data, the first one found will be returned.
Parameters:
funcs— thesource_funcspassed toSource.newuser_data— the user data from the callback
find_source_by_id¶
Finds a Source given a pair of context and ID.
It is a programmer error to attempt to look up a non-existent source.
More specifically: source IDs can be reissued after a source has been
destroyed and therefore it is never valid to use this function with a
source ID which may have already been removed. An example is when
scheduling an idle to run in another thread with idle_add: the
idle may already have run and been removed by the time this function
is called on its (now invalid) source ID. This source ID may have
been reissued, leading to the operation being performed against the
wrong source.
Parameters:
source_id— the source ID, as returned bySource.get_id
find_source_by_user_data¶
Finds a source with the given user data for the callback.
If multiple sources exist with the same user data, the first one found will be returned.
Parameters:
user_data— the user_data for the callback
invoke_full¶
Invokes a function in such a way that context is owned during the
invocation of function.
This function is the same as MainContext.invoke except that it
lets you specify the priority in case function ends up being
scheduled as an idle and also lets you give a DestroyNotify
for data.
The notify function should not assume that it is called from any particular
thread or with any particular context acquired.
Parameters:
priority— the priority at which to runfunctionfunction— function to call
is_owner¶
Determines whether this thread holds the (recursive)
ownership of this MainContext.
This is useful to
know before waiting on another thread that may be
blocking to get ownership of context.
iteration¶
Runs a single iteration for the given main loop.
This involves
checking to see if any event sources are ready to be processed,
then if no events sources are ready and may_block is true, waiting
for a source to become ready, then dispatching the highest priority
events sources that are ready. Otherwise, if may_block is false,
this function does not wait for sources to become ready, and only the highest
priority sources which are already ready (if any) will be dispatched.
Note that even when may_block is true, it is still possible for
MainContext.iteration to return false, since the wait may
be interrupted for other reasons than an event source becoming ready.
Parameters:
may_block— whether the call may block
pending¶
Checks if any sources have pending events for the given context.
pop_thread_default¶
Pops context off the thread-default context stack (verifying that
it was on the top of the stack).
prepare¶
Prepares to poll sources within a main loop.
The resulting information
for polling is determined by calling MainContext.query.
You must have successfully acquired the context with
MainContext.acquire before you may call this function.
push_thread_default¶
Acquires context and sets it as the thread-default context for the
current thread. This will cause certain asynchronous operations
(such as most Gio-based I/O) which are
started in this thread to run under context and deliver their
results to its main loop, rather than running under the global
default main context in the main thread. Note that calling this function
changes the context returned by MainContext.get_thread_default,
not the one returned by MainContext.default, so it does not
affect the context used by functions like idle_add.
Normally you would call this function shortly after creating a new
thread, passing it a MainContext which will be run by a
MainLoop in that thread, to set a new default context for all
async operations in that thread. In this case you may not need to
ever call MainContext.pop_thread_default, assuming you want
the new MainContext to be the default for the whole lifecycle
of the thread.
If you don’t have control over how the new thread was created (e.g.
in the new thread isn’t newly created, or if the thread life
cycle is managed by a ThreadPool), it is always suggested to wrap
the logic that needs to use the new MainContext inside a
MainContext.push_thread_default /
MainContext.pop_thread_default pair, otherwise threads that
are re-used will end up never explicitly releasing the
MainContext reference they hold.
In some cases you may want to schedule a single operation in a
non-default context, or temporarily use a non-default context in
the main thread. In that case, you can wrap the call to the
asynchronous operation inside a
MainContext.push_thread_default /
MainContext.pop_thread_default pair, but it is up to you to
ensure that no other asynchronous operations accidentally get
started while the non-default context is active.
Beware that libraries that predate this function may not correctly
handle being used from a thread with a thread-default context. For example,
see g_file_supports_thread_contexts().
pusher_new¶
Push main_context as the new thread-default main context for the current
thread, using MainContext.push_thread_default, and return a
new GLib.MainContextPusher. Pop with g_main_context_pusher_free().
Using MainContext.pop_thread_default on main_context while a
GLib.MainContextPusher exists for it can lead to undefined behaviour.
Using two GLib.MainContextPushers in the same scope is not allowed,
as it leads to an undefined pop order.
This is intended to be used with g_autoptr(). Note that g_autoptr() is only available when using GCC or clang, so the following example will only work with those compilers:
typedef struct
{
...
GMainContext *context;
...
} MyObject;
static void
my_object_do_stuff (MyObject *self)
{
g_autoptr(GMainContextPusher) pusher = g_main_context_pusher_new (self->context);
// Code with main context as the thread default here
if (cond)
// No need to pop
return;
// Optionally early pop
g_clear_pointer (&pusher, g_main_context_pusher_free);
// Code with main context no longer the thread default here
}
query¶
Determines information necessary to poll this main loop.
You should
be careful to pass the resulting fds array and its length n_fds
as-is when calling MainContext.check, as this function relies
on assumptions made when the array is filled.
You must have successfully acquired the context with
MainContext.acquire before you may call this function.
Parameters:
max_priority— maximum priority source to check
ref¶
Increases the reference count on a MainContext object by one.
release¶
Releases ownership of a context previously acquired by this thread
with MainContext.acquire.
If the context was acquired multiple
times, the ownership will be released only when MainContext.release
is called as many times as it was acquired.
You must have successfully acquired the context with
MainContext.acquire before you may call this function.
remove_poll¶
Removes file descriptor from the set of file descriptors to be polled for a particular context.
Parameters:
fd— aPollFDdescriptor previously added withMainContext.add_poll
unref¶
Decreases the reference count on a MainContext object by one.
If
the result is zero, free the context and free all associated memory.
wait¶
:::warning Deprecated since 2.58 This API is deprecated. :::
Tries to become the owner of the specified context, and waits on cond if
another thread is the owner.
This is the same as MainContext.acquire, but if another thread
is the owner, atomically drop mutex and wait on cond until
that owner releases ownership or until cond is signaled, then
try again (once) to become the owner.
Parameters:
cond— a condition variablemutex— a mutex, currently held
wakeup¶
Wake up context if it’s currently blocking in
MainContext.iteration, causing it to stop blocking.
The context could be blocking waiting for a source to become ready.
Otherwise, if context is not currently blocking, this function causes the
next invocation of MainContext.iteration to return without
blocking.
This API is useful for low-level control over MainContext; for
example, integrating it with main loop implementations such as
MainLoop.
Another related use for this function is when implementing a main loop with a termination condition, computed from multiple threads:
#define NUM_TASKS 10
static gint tasks_remaining = NUM_TASKS; // (atomic)
...
while (g_atomic_int_get (&tasks_remaining) != 0)
g_main_context_iteration (NULL, TRUE);
Then in a thread:
Static functions¶
default¶
Returns the global-default main context.
This is the main context
used for main loop functions when a main loop is not explicitly
specified, and corresponds to the ‘main’ main loop. See also
MainContext.get_thread_default.
get_thread_default¶
Gets the thread-default main context for this thread.
Asynchronous operations that want to be able to be run in contexts other than
the default one should call this method or
MainContext.ref_thread_default to get a
MainContext to add their Sources to. (Note that
even in single-threaded programs applications may sometimes want to
temporarily push a non-default context, so it is not safe to assume that
this will always return NULL if you are running in the default thread.)
If you need to hold a reference on the context, use
MainContext.ref_thread_default instead.
ref_thread_default¶
Gets a reference to the thread-default MainContext for this
thread
This is the same as MainContext.get_thread_default, but it also
adds a reference to the returned main context with MainContext.ref.
In addition, unlike
MainContext.get_thread_default, if the thread-default context
is the global-default context, this will return that
MainContext (with a ref added to it) rather than returning
NULL.