- 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
-
- 16 Sep, 2020 2 commits
-
-
Michael R Fairhurst authored
-
Tong Mu authored
Expose GestureBinding.handlePointerEvent, replacing dispatchEvent as the preferred way to dispatch events (#64846)
-
- 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
-
- 27 Aug, 2020 1 commit
-
-
Ming Lyu (CareF) authored
-
- 24 Aug, 2020 2 commits
-
-
Todd Volkert authored
* Add GestureDetector.onDoubleTapDown() * Review comments
-
David Reveman authored
-
- 12 Aug, 2020 1 commit
-
-
LongCatIsLooong authored
-
- 08 Aug, 2020 1 commit
-
-
creativecreatorormaybenot authored
-
- 06 Aug, 2020 1 commit
-
-
Mouad Debbar authored
-
- 04 Aug, 2020 1 commit
-
-
Jonah Williams authored
-
- 24 Jul, 2020 1 commit
-
-
Kate Lovett authored
-
- 07 Jul, 2020 1 commit
-
-
Tong Mu authored
-
- 11 Jun, 2020 2 commits
-
-
Alexandre Ardhuin authored
* add language version 2.8 in packages/flutter * enable non-nullable analyzer flag
-
Darren Austin authored
-
- 20 Mar, 2020 1 commit
-
-
Tong Mu authored
* Move mouse_tracking to rendering * Move test
-
- 13 Mar, 2020 1 commit
-
-
Tong Mu authored
* TapGestureRecognizer no longer adds the pointer after it resets. * Adds an assertion to make sure TapGestureRecognizer.startTrackingPointer is never called when _down is null
-
- 28 Jan, 2020 1 commit
-
-
Tong Mu authored
-
- 07 Jan, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 06 Jan, 2020 1 commit
-
-
Mouad Debbar authored
-
- 16 Dec, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 06 Dec, 2019 1 commit
-
-
Tong Mu authored
-
- 05 Dec, 2019 1 commit
-
-
Tong Mu authored
-
- 02 Dec, 2019 1 commit
-
-
Tong Mu authored
This PR rewrites MouseTracker's lifecycle, so that mouse callbacks are all triggered in post frame, instead of the current one where some are triggered during the build phase. This PR also changes the onExit callback to MouseRegion, RenderMouseRegion, and MouseTrackerAnnotation, so that it is no longer triggered on dispose.
-
- 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
-
- 20 Nov, 2019 1 commit
-
-
chunhtai authored
-
- 06 Nov, 2019 1 commit
-
-
Taufiq Rahman authored
-
- 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
-
- 11 Oct, 2019 1 commit
- 10 Oct, 2019 3 commits
-
-
Jonah Williams authored
-
Tong Mu authored
* Redesigns the algorithm with which MouseTracker keeps track of states and dispatches events.
-
Tong Mu authored
* Make sendMouseNotifications private
-
- 07 Oct, 2019 1 commit
-
-
Yegor authored
Add more web tests;use blacklist instead of whitelist
-
- 03 Oct, 2019 1 commit
-
-
Tong Mu authored
* Extract pointerData and _equalToEventsOnCriticalFields for simplicity
-
- 02 Oct, 2019 1 commit
-
-
Tong Mu authored
* Extracts the logic of TapGestureRecognizer into an abstract class BaseTapGestureRecognizer * Fixes ModalBarrier unable to dismiss when competing
-
- 30 Sep, 2019 1 commit
-
-
Alexandre Ardhuin authored
* add missing trailing commas * add more missing trailing commas * add more and more missing trailing commas
-
- 26 Sep, 2019 2 commits
-
-
Kristin Ho authored
* MouseRegion documentation claimed that onEnter and onExit would track entry and exit regardless of whether the pointer was down or up * It did such, but when grabbing the value of `event.down` from the passed event, the value was always `false` * PointerEnterEvent and PointerExitEvent were overriding the value passed from PointerEvent in constructors, even if the value was true e.g. in invocations of .fromMouseEvent((PointerMoveEvent...)) * This change now passes the value along to PointerEnter/ExitEvents while providing it a default of false, and updates documentation Fixes #40637
-
Greg Spencer authored
This fixes the mouse hover code to not schedule frames with every mouse move. Before this, it would schedule a post frame callback, and then schedule a frame immediately, even if there was nothing that needed to be updated. Now it will schedule checks for mouse position updates synchronously, unless there's a new annotation, and skip scheduling a new frame in all cases. It has to be async in the case of a new annotation (i.e. a new MouseRegion is added), since when the annotation is added, it hasn't yet painted, and it can't hit test against the new layer until after the paint, so in that case it schedules a post frame callback, but since it's already building a frame when it does that, it doesn't need to schedule a frame. The code also used to do mouse position checks for all mice if only one mouse changed position. I fixed this part too, so that it will only check position for the mouse that changed.
-
- 24 Sep, 2019 2 commits
-
-
Alexandre Ardhuin authored
-
Alexandre Ardhuin authored
-