Lines Matching refs:worker

182 simply create a worker thread—particularly if the operation will likely outlast the activity.
224 your UI from a worker thread—you must do all manipulation to your user interface from the UI
237 "worker" threads).</p>
256 android.widget.ImageView} from the worker thread instead of the UI thread. This can result in
293 difficult to maintain. To handle more complex interactions with a worker thread, you might consider
294 using a {@link android.os.Handler} in your worker thread, to process messages delivered from the UI
296 which simplifies the execution of worker thread tasks that need to interact with the UI.</p>
302 interface. It performs the blocking operations in a worker thread and then publishes the results on
322     /** The system calls this to perform work in a worker thread and
337 part that should be done on a worker thread and the part that should be done on the UI thread.</p>
346 on a worker thread</li>
358 <p class="caution"><strong>Caution:</strong> Another problem you might encounter when using a worker
361 (such as when the user changes the screen orientation), which may destroy your worker thread. To