The runnable examples in this guide are presented for JavaFx. Starting coroutine in UI event handlers without dispatch.Structured concurrency, lifecycle and coroutine parent-child hierarchy.You can use any of them as an example to write the corresponding context object for your favourite UI library, even if it is not included out of the box here. This guide covers all UI libraries simultaneously, because each of these modules consists of just one object definition that is a couple of pages long. For example, if you are writing JavaFx application, you can use either Dispatchers.Main or Dispachers.JavaFx extension, it will be the same object. kotlinx-coroutines-swing - Dispatchers.Swing context for Swing UI applications.Īlso, UI dispatcher is available via Dispatchers.Main from kotlinx-coroutines-core and corresponding implementation (Android, JavaFx or Swing) is discovered by ServiceLoader API.kotlinx-coroutines-javafx - Dispatchers.JavaFx context for JavaFX UI applications.kotlinx-coroutines-android - Dispatchers.Main context for Android applications.In particular, routines has three modules that provide coroutine context for different UI application libraries: With respect to coroutines, it means that you need an appropriate coroutine dispatcher context that confines the coroutine execution to this main UI thread. They have the single main thread where all state of the UI is confined, and all updates to the UI has to happen in this particular thread.
This guide assumes familiarity with basic coroutine concepts that are covered in Guide to routines and gives specific examples on how to use coroutines in UI applications.Īll UI application libraries have one thing in common.
0 kommentar(er)
