- 14 Apr, 2022 1 commit
-
-
Michael Goderbauer authored
-
- 07 May, 2021 1 commit
-
-
Kate Lovett authored
-
- 28 Apr, 2021 1 commit
-
-
Todd Volkert authored
This adds support for GestureDetector.onLongPressDown and GestureDetector.onLongPressCancel, allowing callers to register interest in the initial pointer contact that might turn into a long-press (and the associated cancel event if the gesture loses).
-
- 03 Apr, 2021 1 commit
-
-
Alexandre Ardhuin authored
-
- 30 Mar, 2021 1 commit
-
-
Alexandre Ardhuin authored
-
- 17 Sep, 2020 2 commits
-
-
Matěj Žídek authored
-
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
-
- 08 Aug, 2020 1 commit
-
-
creativecreatorormaybenot authored
-
- 28 Jul, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 11 Jun, 2020 1 commit
-
-
Alexandre Ardhuin authored
* add language version 2.8 in packages/flutter * enable non-nullable analyzer flag
-
- 01 May, 2020 1 commit
-
-
Greg Spencer 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
-
- 29 Oct, 2019 1 commit
-
-
Pieter van Loon authored
Drag from the right is no more Longpress is now only 100ms instead of 500 Added optional duration field to longpressgesturerecognizer Added controller field to material scrollbar api Haptic feedback only triggers when scrollbar is fully expanded Added haptic feedback when releasing the scrollbar after dragging it
-
- 31 Jul, 2019 1 commit
-
-
Justin McCandless authored
You can drag the cupertinoscrollbar if you pass an active scrollcontroller to the scrollbar.
-
- 13 Jul, 2019 1 commit
-
-
Hey24sheep authored
-
- 04 Jun, 2019 1 commit
-
- 03 Jun, 2019 1 commit
-
-
Tong Mu authored
- A refactor that moves the semantics declaration from detectors to recognizers to allow custom recognizers to respond to semantic gectures. - Renames all handlers related to semantics from Gesture* to Semantics*.
-
- 31 May, 2019 1 commit
-
-
Michael Goderbauer authored
-
- 20 May, 2019 1 commit
-
- 01 May, 2019 1 commit
-
-
Jonah Williams authored
This reverts commit fea2c7d6.
-
- 30 Apr, 2019 1 commit
-
- 29 Apr, 2019 2 commits
-
-
Jonah Williams authored
This reverts commit 727e7e82.
-
Tong Mu authored
* Callbacks of tap, long press, drag, and double tap GR respond to only primary events. * Add "secondary" callbacks to tap. * Recognizers only compete on events if there are any related callbacks. * Add "kSecondaryButton" constant.
-
- 01 Mar, 2019 1 commit
-
-
Mouad Debbar authored
-
- 25 Feb, 2019 1 commit
-
-
xster authored
-
- 20 Feb, 2019 1 commit
-
-
xster authored
-
- 12 Feb, 2019 1 commit
-
-
xster authored
-
- 29 Jan, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 16 Oct, 2018 1 commit
-
-
jslavitz authored
* add onLongPressUp geasture which is fired when a long-press ends
-
- 14 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 13 Jun, 2018 1 commit
-
-
Chris Bracken authored
fuchsia_tester.dart still assumes Dart 1. Previously, it ran tests directly from source, flutter_platform.dart automatically runs a kernel compile when operating in Dart 2 mode, but this assumes a functional Dart SDK is available in the artifacts directly, and fuchsia_tester.dart mocks out the artifacts directory with an empty temp dir. Remaining work is: 1. Get the frontend server building as a dependency on Fuchsia. 2. Patch fuchsia_tester.dart to use a valid Dart SDK and frontend server. This also reverts migration to Dart 2 typedef syntax. This reverts commit 6c56bb24. (#18362) This reverts commit 3daebd05. (#18316)
-
- 11 Jun, 2018 1 commit
-
-
Greg Spencer authored
Now that Dart 1 is turned off, reapplying my change to turn on the prefer_generic_function_type_aliases analysis option, and fix all the typedefs to Dart 2 preferred syntax. Also eliminated the unused analysis_options_repo.yaml file and turned on public_member_api_docs in analysys_options.yaml. No logic changes, just changing the typedef syntax for all typedefs, and updating analysis options.
-
- 30 May, 2018 2 commits
-
-
Greg Spencer authored
Revert "Update typedef syntax to use Function notation and turn on lint for old notation. (#18035)" (#18041) This reverts commit 32586020.
-
Greg Spencer authored
Fixes #18028 Just changes typedef declarations, no logic changes.
-
- 24 Jan, 2018 1 commit
-
-
Vyacheslav Egorov authored
-
- 17 Nov, 2017 1 commit
-
-
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.
-
- 03 Aug, 2017 1 commit
-
-
Jacob Richman authored
Add Diagnosticable base class and documentation
-
- 27 Jul, 2017 1 commit
-
-
Ian Hickson authored
It was 8.0. It's now arbitrarily 18.0. Changing this required adjusting some tests. Adjusting the tests required debugging the tests. Debugging the tests required some tools to help debugging gesture recognizers and gesture arenas, so I added some. It also required updating some toString() methods which resulted in some changes to the tree diagnostics logic. Also I cleaned up some docs while I was at it.
-
- 22 Jan, 2017 1 commit
-
-
Ian Hickson authored
-