pub struct Mainloop {
    pub _inner: Rc<MainloopInner<MainloopInternal>>,
}
Expand description

This acts as a safe interface to the internal PA Mainloop.

The mainloop object pointers are further enclosed here in a ref counted wrapper, allowing this outer wrapper to have clean methods for creating event objects, which can cleanly pass a copy of the inner ref counted mainloop object to them. Giving this to events serves two purposes, firstly because they need the API pointer, secondly, it ensures that event objects do not outlive the mainloop object.

Fields

_inner: Rc<MainloopInner<MainloopInternal>>

The ref-counted inner data

Implementations

Allocate a new threaded main loop object.

You have to call start before the event loop thread starts running.

Start the event loop thread.

Terminate the event loop thread cleanly. Make sure to unlock the mainloop object before calling this function.

Lock the event loop object, effectively blocking the event loop thread from processing events. You can use this to enforce exclusive access to all objects attached to the event loop. This lock is recursive. This function may not be called inside the event loop thread. Events that are dispatched from the event loop thread are executed with this lock held.

Unlock the event loop object, inverse of lock.

Wait for an event to be signalled by the event loop thread. You can use this to pass data from the event loop thread to the main thread in a synchronized fashion. This function may not be called inside the event loop thread. Prior to this call the event loop object needs to be locked using lock. While waiting the lock will be released. Immediately before returning it will be acquired again. This function may spuriously wake up even without signal being called. You need to make sure to handle that!

Signal all threads waiting for a signalling event in wait. If wait_for_accept is non-zero, do not return before the signal was accepted by an accept call. While waiting for that condition the event loop object is unlocked.

Accept a signal from the event thread issued with signal.

This call should only be used in conjunction with signal with wait_for_accept as true.

Return the return value as specified with the main loop’s quit routine (used internally by threaded mainloop).

Return the main loop abstraction layer vtable for this main loop.

There is no need to free this object as it is owned by the loop and is destroyed when the loop is freed.

Talking to PA directly with C requires fetching this pointer explicitly via this function. This is actually unnecessary through this binding. The pointer is retrieved automatically upon Mainloop creation, stored internally, and automatically obtained from it by functions that need it.

Returns true when called from within the event loop thread.

Sets the name of the thread.

Trait Implementations

Create a new IO event Read more
Create a new timer event Read more
Create a new monotonic-based timer event Read more
Create a new deferred event Read more
Run the specified callback once from the main loop using an anonymous defer event. If the mainloop runs in a different thread, you need to follow the mainloop implementation’s rules regarding how to safely create defer events. In particular, if you’re using ::mainloop::threaded, you must lock the mainloop before calling this function. Read more
Call quit
Initialize the UNIX signal subsystem and bind it to the specified main loop
Cleanup the signal subsystem

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

The type returned in the event of a conversion error.
Performs the conversion.
The type returned in the event of a conversion error.
Performs the conversion.