Lifecycles, Coroutines and Scopes | Alejandro Serrano Mena

Поділитися
Вставка
  • Опубліковано 24 гру 2024

КОМЕНТАРІ • 10

  • @alexismanin5239
    @alexismanin5239 4 місяці тому +2

    Very clear, it really helped me better understand the power of coroutine scopes 👍

  • @aungkhanthtoo7678
    @aungkhanthtoo7678 5 місяців тому +6

    Great talk!

  • @evgeniyemelyanov7281
    @evgeniyemelyanov7281 5 місяців тому +2

    Great explanation, thanks!

  • @DungNguyen-yp9jd
    @DungNguyen-yp9jd 2 місяці тому

    nice job!

  • @Jlin1982
    @Jlin1982 5 місяців тому +1

    Greate talk

  • @azzdine7453
    @azzdine7453 4 місяці тому

    Guys someone help me please, i'am doing very fast update to the local database (room) the problem is sometimes the database is not updating, i tried viewModelLunch scope and dispatcher IO , any one can help or have idea please and thank you ..

    • @alexanderbernat182
      @alexanderbernat182 4 місяці тому +1

      You need to make a scope for database handling wider than your view model. For example, create a repository tied to app lifecycle. In this case your jobs will not be cancelled by narrow view model scopes.

    • @azzdine7453
      @azzdine7453 4 місяці тому

      @@alexanderbernat182 I will try that thank you

  • @Heksapoda
    @Heksapoda 5 місяців тому

    Is it mean that Activity initiate a Thread and exist until the Activity destroyed then other components could use that Thread to do asynchronous job?

    • @rahu-gill
      @rahu-gill 4 місяці тому

      no, all code you write in an activity is by default run in the single ui thread