1. 27 Jul, 2018 1 commit
  2. 23 Jul, 2018 1 commit
  3. 16 Jul, 2018 2 commits
  4. 05 Jun, 2018 1 commit
  5. 12 Mar, 2018 1 commit
  6. 02 Feb, 2018 1 commit
  7. 09 Jan, 2018 1 commit
  8. 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
  9. 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
  10. 21 Sep, 2017 1 commit
  11. 23 Aug, 2017 1 commit
  12. 18 Aug, 2017 1 commit
  13. 04 Aug, 2017 3 commits
  14. 12 Jun, 2017 1 commit
  15. 05 Jun, 2017 1 commit
  16. 05 May, 2017 1 commit
  17. 03 May, 2017 1 commit
  18. 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
  19. 16 Mar, 2017 1 commit
  20. 04 Mar, 2017 1 commit
  21. 18 Feb, 2017 1 commit
  22. 19 Jan, 2017 2 commits
    • Adam Barth's avatar
      Improve Route lifecycle (#7526) · 23361d5a
      Adam Barth authored
      Previously the navigator wouldn't always call Route.dispose when it was
      removed from the tree. After this patch, the navigator remembers popped
      routes so that it can call dispose on them when it is removed from the
      tree.
      
      Also, improve some error messages around calling dispose() more than
      once on routes and AnimationControllers.
      
      Fixes #7457
      23361d5a
    • Adam Barth's avatar
      Remove Force and SpringForce (#7532) · 7d5f172a
      Adam Barth authored
      The only client of this machinery was AnimationController.fling, but
      it's easier for that function to just create the simulation it needs
      directly.
      
      Fixes #7216
      7d5f172a
  23. 19 Nov, 2016 1 commit
  24. 17 Nov, 2016 1 commit
  25. 28 Sep, 2016 1 commit
    • Ian Hickson's avatar
      Fix globalToLocal and update spinning_mixed (#6035) · e01592a0
      Ian Hickson authored
      * globalToLocal was just broken when there was a rotation and a
        translation at the same time. This fixes that and adds a test.
      
      * update graphic used by spinning_mixed since the old one went 404.
      
      * simplify some of the code in the demo.
      
      * fix MatrixUtils.transformPoint to be consistent with how we transform
        points elsewhere.
      
      * stop transforming points elsewhere, just use
        MatrixUtils.transformPoint.
      
      * make the Widget binding handle not having a root element.
      
      * make the spinning_mixed demo update its widget tree.
      e01592a0
  26. 26 Sep, 2016 2 commits
  27. 22 Sep, 2016 1 commit
  28. 04 Aug, 2016 1 commit
  29. 13 Jun, 2016 1 commit
  30. 12 May, 2016 1 commit
  31. 27 Apr, 2016 1 commit
  32. 20 Apr, 2016 1 commit
    • Ian Hickson's avatar
      Reset _simulation at the end of a fling (#3435) · 112f2cc3
      Ian Hickson authored
      Also a bit of code cleanup.
      
      The key part of this patch is the addition in `_endScroll` to reset
      `_simulation`. It seems like this was the one place where it's possible
      for us to end the animation but not reset our state. Since we assert
      that are state is coherent, we were hitting asserts when a fling
      finished and then you interacted with the widget again.
      112f2cc3
  33. 06 Apr, 2016 1 commit
  34. 23 Mar, 2016 1 commit
    • Adam Barth's avatar
      Scrollable physics should be reasonable when sizes change · f7f1259b
      Adam Barth authored
      Previously, when the content extent changed during a scroll interaction, we'd
      stop the current scroll interaction and reset the scroll offset. Now we try to
      continue the scroll interaction (e.g., drag, fling, or overscroll) even through
      the underlying scroll behavior has changed.
      
      For physics-based scroll interactions, we keep the current position and
      velocity and recompute the operative forces. For drag interactions, we keep the
      current position and continue to let the user drag the scroll offset.
      
      After this patch, we still disrupt non-physical scroll animations that are
      operating outside the new scroll bounds because it's not clear how we can
      sensibly modify them to work with the new scroll bounds.
      f7f1259b
  35. 21 Mar, 2016 1 commit
    • Ian Hickson's avatar
      Provide more documentation for MojoShell · bef6ff3b
      Ian Hickson authored
      As usual, as I was doing this I ran into some stuff that seemed hard
      to document as-is and so I changed it. In this case, in the "http"
      library. The new code is more or less equivalent, I think, but the
      resulting documentation makes it more obvious that it's wrong...
      bef6ff3b