- 20 Sep, 2023 1 commit
-
-
Kostia Sokolovskyi authored
-
- 25 Aug, 2023 1 commit
-
-
Kate Lovett authored
-
- 15 May, 2023 1 commit
-
-
Tomasz Gucio authored
-
- 22 Mar, 2023 1 commit
-
-
Michael Goderbauer authored
Remove 1745 decorative breaks
-
- 14 Mar, 2023 1 commit
-
-
Kate Lovett authored
Update ScrollableDetails for 2D scrolling
-
- 31 Oct, 2022 1 commit
-
-
Greg Spencer authored
-
- 07 May, 2022 1 commit
-
-
xubaolin authored
-
- 27 Apr, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 13 Apr, 2022 1 commit
-
-
Callum Moffat authored
* Implement trackpad gestures in framework * Touch and Pan/Zoom pointers have separate IDs now * Handle trackpad pointer device type * Respect supportedDevices for pan/zoom events * Update after rebase * Fix check failures * Avoid error with very short drags * Address feedback * Refactor drag event handler * Address more feedback * Add some missing punctuation
-
- 04 Apr, 2022 1 commit
-
- 31 Mar, 2022 1 commit
-
- 29 Mar, 2022 1 commit
-
-
chunhtai authored
-
- 20 Oct, 2021 1 commit
-
-
Kate Lovett authored
-
- 07 Oct, 2021 1 commit
-
-
Kate Lovett authored
-
- 11 Aug, 2021 1 commit
-
-
Kate Lovett authored
-
- 15 Oct, 2020 1 commit
-
-
Greg Spencer authored
-
- 17 Sep, 2020 1 commit
-
-
Jonah Williams authored
Deprecate VelocityTracker default constructor and added VelocityTracker.withKind constructor (#66043) We've gotten feedback that the VelocityTracker change was disruptive, though it did not break any of the flutter framework or customer tests. In order to make the change non-breaking, PointerDeviceKind parameter can be made optional. Nevertheless, this parameter should be provided so that the existing touch handlers can use more accurate gestures on mouse/stylus inputs, so we can encourage this by deprecating the default constructor and pointing users towards the VelocityTracker.withKind constructor that takes a non-optional parameter
-
- 08 Sep, 2020 1 commit
-
-
Jonah Williams authored
Currently the framework uses fairly large "hit slop" values to disambiguate taps from drags/pans. This makes sense on touch devices where the interaction is not very precise, on mice however it can feel as if the UI is lagging. This is immediately noticeable on our infra dashboard, where it takes almost half of a grid square of drag before the actual drag kicks in. One potential solution is to always use smaller constants depending on whether the interaction is mouse or touch based. The only reasonable choice is to use the pointer device kind and not target platform - same platform can have different input sources. This requires exposing the pointer device kind in a few new places in several of the gesture detectors, and using the enum to compute the correct hit slop from an expanded set of constants. This almost works, however there are a few places (notably ListViews) which uses the touch hit slop as a default value in scroll physics. It does not seem like it will be easy to disambiguate a user provided scroll physics constant from the default and/or adjust it somehow - this might require significant changes to scroll physics which I have left out of this PR. This PR does not adjust: kTouchSlop used in scroll_physics.dart's minFlingDistance kTouchSlop used in PrimaryPointerGestureRecognizer/LongPressGestureRecognizer
-
- 12 Aug, 2020 1 commit
-
-
LongCatIsLooong authored
-
- 11 Jun, 2020 1 commit
-
-
Alexandre Ardhuin authored
* add language version 2.8 in packages/flutter * enable non-nullable analyzer flag
-
- 27 Jan, 2020 1 commit
-
-
Dan Field authored
-
- 17 Jan, 2020 1 commit
-
-
Anthony authored
[a11y] Make sure RenderFractionalTranslation updates its semantics after the translation field is set (#48985)
-
- 16 Jan, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 16 Dec, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 20 Jun, 2018 1 commit
-
-
Ian Hickson authored
The new matcher package deprecates isInstanceOf which seems eggregious.
-
- 19 Jun, 2018 1 commit
-
-
Greg Spencer authored
-
- 01 Feb, 2018 1 commit
-
-
Ian Hickson authored
-
- 25 Apr, 2017 1 commit
-
-
Adam Barth authored
This patch reworks some of the guts of scrolling to make it easier to implement nested scrolling effects. The actually nested scrolling effect will be included in a later patch.
-
- 21 Apr, 2017 1 commit
-
-
Alexandre Ardhuin authored
* make @immutable const * fix build
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 17 Feb, 2017 1 commit
-
-
Adam Barth authored
Rename all the "2" classes related to scrolling to remove the "2". Now that the old scrolling code is gone, we don't need to use the suffix.
-
- 14 Feb, 2017 1 commit
-
-
Adam Barth authored
Also, rename ScrollableMetrics to ScrollMetrics, which follows the naming convention for most of the other classes (e.g., ScrollPosition, ScrollPhysics). Finally, fix a bug whereby SingleChildScrollView could not have a GlobalKey, because, write test, find bug.
-
- 01 Feb, 2017 1 commit
-
-
Adam Barth authored
This patch removes unnecessary uses of scrollableKey from tests. Scrollable2 will likely use a different mechanism for identifying itself, so we want to focus on the uses of scrollableKey that will need to be addressed in the new implementation.
-
- 09 Dec, 2016 1 commit
-
-
Alexandre Ardhuin authored
-
- 19 Nov, 2016 1 commit
-
-
Ian Hickson authored
-
- 07 Nov, 2016 1 commit
-
-
Ian Hickson authored
-
- 07 Oct, 2016 1 commit
-
-
Adam Barth authored
This patch adds `@checked` everywhere is needed to remove the `strong_mode_invalid_method_override` strong mode error.
-
- 14 Sep, 2016 1 commit
-
-
Hans Muller authored
-