1. 20 Jun, 2019 1 commit
  2. 16 May, 2019 1 commit
  3. 04 Apr, 2019 1 commit
  4. 29 Jan, 2019 1 commit
  5. 24 Jan, 2019 2 commits
  6. 22 Jan, 2019 1 commit
    • jslavitz's avatar
      Transition Curve Fix (#25488) · cf4fc966
      jslavitz authored
      * Changes Cupertino page transition curves to make paging animations more similar to those of native iOS
      cf4fc966
  7. 08 Nov, 2018 1 commit
  8. 05 Nov, 2018 1 commit
    • Greg Spencer's avatar
      Rewrite the analyze-sample-code script to also analyze snippets (#23893) · 202b045b
      Greg Spencer authored
      This rewrites the sample code analysis script to be a little less of a hack (but still not pretty), and to handle snippets as well.
      
      It also changes the semantics of how sample code is handled: the namespace for the sample code is now limited to the file that it appears in, so some additional "Examples can assume:" blocks were added. The upside of this is that there will be far fewer name collisions.
      
      I fixed the output too: no longer will you get 4000 lines of numbered output with the error at the top and have to grep for the actual problem. It gives the filename and line number of the original location of the code (in the comment in the tree), and prints out the source code on the line that caused the problem along with the error.
      
      For snippets, it prints out the location of the start of the snippet and the source code line that causes the problem. It can't print out the original line, because snippets get formatted when they are written, so the line might not be in the same place.
      202b045b
  9. 17 Oct, 2018 1 commit
  10. 16 Oct, 2018 1 commit
  11. 23 Sep, 2018 1 commit
  12. 12 Sep, 2018 1 commit
  13. 07 Sep, 2018 1 commit
  14. 29 Aug, 2018 1 commit
  15. 23 Aug, 2018 1 commit
  16. 02 Aug, 2018 1 commit
  17. 27 Jul, 2018 1 commit
  18. 23 Jul, 2018 1 commit
  19. 16 Jul, 2018 2 commits
  20. 05 Jun, 2018 1 commit
  21. 12 Mar, 2018 1 commit
  22. 02 Feb, 2018 1 commit
  23. 09 Jan, 2018 1 commit
  24. 22 Nov, 2017 1 commit
    • Kyle Bradshaw's avatar
      AnimationController reset() method (#13044) · 3dc32873
      Kyle Bradshaw authored
      * AnimationController reset() method
      
      Just a simple convenience method to fix #13039
      
      * Added `reset()` test
      
      * More test expectations
      
      Per feedback.
      
      * Removed test print
      
      * Improved documentation of reset()
      
      * Add controller.reverse to test
      3dc32873
  25. 17 Nov, 2017 1 commit
    • Greg Spencer's avatar
      Fix spelling errors in all the dartdocs. (#13061) · 0259be90
      Greg Spencer authored
      I got tired of drive-by spelling fixes, so I figured I'd just take care of them all at once.
      
      This only corrects errors in the dartdocs, not regular comments, and I skipped any sample code in the dartdocs. It doesn't touch any identifiers in the dartdocs either. No code changes, just comments.
      0259be90
  26. 21 Sep, 2017 1 commit
  27. 23 Aug, 2017 1 commit
  28. 18 Aug, 2017 1 commit
  29. 04 Aug, 2017 3 commits
  30. 12 Jun, 2017 1 commit
  31. 05 Jun, 2017 1 commit
  32. 05 May, 2017 1 commit
  33. 03 May, 2017 1 commit
  34. 15 Apr, 2017 1 commit
    • Ian Hickson's avatar
      Support chaining await calls on controllers (#9389) · 14e728d0
      Ian Hickson authored
      With this patch, you can do:
      
      ```dart
         Future<Null> foo() async {
           try {
             await controller.forward().orCancel;
             await controller.reverse().orCancel;
             await controller.forward().orCancel;
           } on TickerCanceled {
             // did not complete
           }
         }
      ```
      
      ...in a State's async method, and so long as you dispose of the
      controller properly in your dispose, you'll have a nice way of doing
      animations in sequence without leaking the controller. try/finally
      works as well, if you need to allocate resources and discard them when
      canceled.
      
      Simultaneously, you can do:
      
      ```dart
         Future<Null> foo() async {
           await controller.forward().orCancel;
           await controller.reverse().orCancel;
           await controller.forward().orCancel;
         }
      ```
      
      ...and have the same effect, where the method will just silently hang
      (and get GC'ed) if the widget is disposed, without leaking anything,
      if you don't need to catch the controller being killed.
      
      And all this, without spurious errors for uncaught exceptions on
      controllers.
      14e728d0
  35. 16 Mar, 2017 1 commit
  36. 04 Mar, 2017 1 commit