1. 30 Nov, 2017 1 commit
  2. 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
  3. 20 Sep, 2017 1 commit
    • xster's avatar
      Scroll momentum builds on iOS with repeated flings (#11685) · 59b94185
      xster authored
      * Record original pointer event timestamp
      
      * review
      
      * review
      
      * review
      
      * Matched motions with iOS. Didn’t add overscroll spring clamps and fix tests yet.
      
      * clamp max overscroll transfer
      
      * Add test
      
      * review notes, moved things around
      
      * remove function passing indirection
      
      * review
      
      * Replace stopwatch with timestamp from #11988
      
      * move static
      
      * Review
      59b94185
  4. 21 Jun, 2017 3 commits
  5. 02 Jun, 2017 1 commit
  6. 06 May, 2017 1 commit
  7. 05 May, 2017 1 commit
  8. 02 May, 2017 1 commit
    • Ian Hickson's avatar
      Tapping a ScrollView during overscroll got it stuck. (#9721) · f64bfba8
      Ian Hickson authored
      Fixes https://github.com/flutter/flutter/issues/8476
      
      More detailed list of changes in this patch:
      
      * Replaced the didTouch special logic with more generic logic that
        uses Activities instead. Now instead when you tap down the
        Scrollable calls `hold()` which begins a HoldScrollActivity which is
        a hybrid of DragStartDetails and IdleScrollActivity and can be
        canceled. When you let go, it gets canceled and that goes ballistic.
      
      * Make DragGestureRecognizer more aggressive about grabbing pointers,
        otherwise a second pointer in a situation with competing horizontal
        and vertical recognizers always gets taken by the other one.
      
      * Fixed the _GestureSemantics widget to call the "down" callbacks so
        that it follows the same pattern as "real" interactions.
      
      * Added tests for the above.
      
      * Added a hashCode to ScrollActivity.toString (and subclasses).
      
      * Added a toString to ScrollDragController, and include it in
        DragScrollActivity's toString.
      
      * s/coorindator/coordinator/
      
      * Add a comment in DragStartDetails to distinguish it from the
        otherwise identical DragDownDetails, so we're not tempted to merge
        them.
      f64bfba8
  9. 30 Apr, 2017 1 commit
  10. 27 Apr, 2017 1 commit
  11. 25 Apr, 2017 1 commit