1. 09 1月, 2020 1 次提交
  2. 08 1月, 2020 1 次提交
  3. 07 1月, 2020 1 次提交
  4. 04 1月, 2020 1 次提交
  5. 03 12月, 2019 1 次提交
  6. 26 11月, 2019 1 次提交
  7. 21 11月, 2019 1 次提交
  8. 15 11月, 2019 2 次提交
  9. 13 11月, 2019 1 次提交
  10. 09 11月, 2019 1 次提交
  11. 08 11月, 2019 1 次提交
  12. 06 11月, 2019 2 次提交
  13. 05 11月, 2019 3 次提交
  14. 01 11月, 2019 3 次提交
  15. 29 10月, 2019 2 次提交
  16. 25 10月, 2019 3 次提交
  17. 24 10月, 2019 3 次提交
  18. 03 10月, 2019 1 次提交
    • S
      Distinguish resource set from request complete in Glide's RequestCoordinators · 690f8152
      Sam Judd 提交于
      A request might have it's thumbnail complete, but not it's full. It's
      not complete, but it has a resource set. If it has a resource set, and a
      parent's request fails, we shouldn't replace the thumbnail with the
      error placeholder.
      
      Complicating matters is that we have another way in which we want to
      know if a resource is set. SingleRequest wants to know if its the first
      request in the set so it can tell its RequestListener. That requires
      walking up the request coordinator tree and then back down.
      
      To solve the first issue, we check the requests explicitly and walk down
      the tree to see if any has set a resource, regardless of its state.
      
      To solve the second issue, we introduce a getRoot() method on
      RequestCoordinator that can be used by SingleRequest to walk down the
      entire tree.
      
      PiperOrigin-RevId: 272448635
      690f8152
  19. 02 10月, 2019 2 次提交
  20. 28 9月, 2019 8 次提交
  21. 27 9月, 2019 1 次提交