Lines Matching refs:thread

12    A user interface thread must remain responsive to user requests, and
22    Graphical user interfaces often have a dedicated thread ("GUI
23    thread") for servicing user interactions. The thread must remain
27    thread takes part in the long running computation, it will not be
37    -  The GUI thread services an event loop.
40    -  The GUI thread needs to offload work onto other threads without
44    -  The GUI thread must be responsive to the event loop and not become
64    The GUI thread offloads the work by firing off a task to do it using
66    When finished, the task posts an event to the GUI thread to indicate that the work is done.
67    The semantics of ``enqueue`` cause the task to eventually run on a worker thread
68    distinct from the calling thread.
71    by the GUI thread; items in blue are executed by another thread.
83    each event, the GUI thread calls a user-defined function ``WndProc`` to process an event.
93       // Queue for transmitting results from enqueued task to GUI thread.
97       // GUI thread's private copy of most recently computed result.
106                          // User requested a long computation. Delegate it to another thread.
135    The GUI thread processes long computations as follows:
138    #. The GUI thread calls ``LongRunningWork``, which hands off the work
139       to a worker thread and immediately returns.
142    #. The GUI thread continues servicing the event loop. If it has to
148    into ResultQueue, and sends a message WM_POP_FOO to the GUI thread.
151    #. The GUI thread services a ``WM_POP_FOO`` message by popping an
169              // Notify GUI thread that result is available.
185    even if no thread explicitly waits on the task. In contrast, ``oneapi::tbb::task_group::run`` may
189    results back to the GUI thread. Since only the most recent result
192    worker while the GUI thread was holding a lock on the mutex, and vice
199    thread can pop from ``ResultQueue`` into a temporary variable, check