- 01 Aug, 2019 1 commit
-
-
Yegor authored
* Sync the value kMaxUnsignedSMI for the Web * update events.dart docs
-
- 31 May, 2019 1 commit
-
-
Michael Goderbauer authored
-
- 30 May, 2019 1 commit
-
-
Greg Spencer authored
This PR solves two problems: currently, the onExit is called for a mouse pointer the moment the removal message is received, except that by the time it actually calls it, there is no _lastEvent for it in the mouse tracker (it's already been removed), resulting in an event being passed to the onExit that contains nulls for the position. Also, removePointer events don't actually get created with a position, although they easily could be, so that even the the _lastEvent in the mouse tracker were still populated, it would still give a null position and delta. This PR adds support for the position and delta in a PointerRemovedEvent, and populates them. In addition, when a remove event is received, it doesn't actually remove the pointer until the mouse position check that gets scheduled actually happens.
-
- 20 May, 2019 1 commit
-
- 03 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.
-
- 22 Apr, 2019 1 commit
-
-
Tong Mu authored
* Down and Move have default buttons = kPrimary.
-
- 10 Apr, 2019 2 commits
-
-
Tong Mu authored
* Remove pressure from PointerHoverEvent ctor
- 04 Apr, 2019 2 commits
-
-
Tong Mu authored
* Add constants `kPrimaryButton`, `kTouchContact` and `kStylusContact` * PointerDownEvent and PointerMoveEvent will always set the 0x01 bit on buttons
-
Tong Mu authored
* Fix: ui.PointerChange.remove might contain position change, but we used to expand it into a Cancel and Remove, neither of which allows position change. A Hover event is added, and a test is updated accordingly. * Fixed the issue where a PointerMoveEvent and a PointerCancelEvent do not receive the correct pressure. * Refactor the calculation of delta into deltaTo.
-
- 27 Mar, 2019 1 commit
-
-
Dwayne Slater authored
Avoids an implicit downcast + crash in MouseTracker, since the last pointer event can be a Move or Down event, in addition to Hover.
-
- 11 Mar, 2019 1 commit
-
-
stuartmorgan authored
Adds support for discrete scroll events, such as those sent by a scroll wheel. Includes the plumbing to convert, dispatch, and handle these events, as well as Scrollable support for consuming them.
-
- 01 Mar, 2019 1 commit
-
-
Alexandre Ardhuin authored
* add trailing commas on list/map/parameters * add trailing commas on Invocation with nb of arg>1 * add commas for widget containing widgets * add trailing commas if instantiation contains trailing comma * revert bad change
-
- 25 Feb, 2019 1 commit
-
-
stuartmorgan authored
Rather than building a description string by hand, use Diagnosticable properties. Simplifies output, since many fields have uninteresting default values in many cases, and makes it easier to add more loggable properties in subclasses. Issue #28014
-
- 29 Jan, 2019 1 commit
-
-
Greg Spencer authored
This implements support for hovering mouse pointers, so that mice connected to Android devices, and ChromeOS devices running Android apps will work properly. It teaches flutter_test about hover events, which required changing how they are created and used. Also modifies AnnotatedRegion to allow a region that can be located someplace other than just the origin. Along with tests for all of the above. Fixes #5504
-
- 20 Dec, 2018 1 commit
-
-
jslavitz authored
* adds Force Press gesture detector and recognizer
-
- 09 Nov, 2018 1 commit
-
-
Stanislav Baranov authored
-
- 05 Nov, 2018 1 commit
-
-
Stanislav Baranov authored
-
- 26 Oct, 2018 1 commit
-
-
Stanislav Baranov authored
-
- 25 Jul, 2018 1 commit
-
-
amirh authored
These are bugs uncovered by the integration test for embedded Android views: * Some PointerEvents were constructed with radiusMinor set to radiusMajor. * Some PointerEvents were missing radiusMajor/radiusMinor. * The pressure parameter was not passed to PointerUpEvent. * radiusMin, radiusMax, radiusMinor, and radiusMajor were not converted from physical pixels to logical. Sending the fixes without a test as the bugs are covered by the integration test that is going to land soon.
-
- 13 Jun, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 05 Jun, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 12 Mar, 2018 1 commit
-
-
Jason Simmons 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.
-
- 24 Sep, 2017 1 commit
-
-
Ian Hickson authored
-
- 10 Aug, 2017 1 commit
-
-
xster authored
* Add synthesized property to pointer events * test
-
- 16 May, 2017 1 commit
-
-
Ian Hickson authored
Previously we used logical pixels. This made the accessibility metrics tiny on modern devices, since the OS works in physical units. Also add a bit more debugging info and some docs.
-
- 19 Apr, 2017 1 commit
-
-
Adam Barth authored
Turns out we have many immutable classes. Fixes #6892
-
- 12 Apr, 2017 1 commit
-
-
Ian Hickson authored
* Manually fix every use of Point.x and Point.y Some of these were moved to dx/dy, but not all. * Manually convert uses of the old gradient API * Remove old reference to Point. * Mechanical changes I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\bPoint[.]origin\b/Offset.zero/g' git ls-files -z | xargs -0 sed -i 's/\bPoint[.]lerp\b/Offset.lerp/g' git ls-files -z | xargs -0 sed -i 's/\bnew Point\b/new Offset/g' git ls-files -z | xargs -0 sed -i 's/\bconst Point\b/const Offset/g' git ls-files -z | xargs -0 sed -i 's/\bstatic Point /static Offset /g' git ls-files -z | xargs -0 sed -i 's/\bfinal Point /final Offset /g' git ls-files -z | xargs -0 sed -i 's/^\( *\)Point /\1Offset /g' git ls-files -z | xargs -0 sed -i 's/ui[.]Point\b/ui.Offset/g' git ls-files -z | xargs -0 sed -i 's/(Point\b/(Offset/g' git ls-files -z | xargs -0 sed -i 's/\([[{,]\) Point\b/\1 Offset/g' git ls-files -z | xargs -0 sed -i 's/@required Point\b/@required Offset/g' git ls-files -z | xargs -0 sed -i 's/<Point>/<Offset>/g' git ls-files -z | xargs -0 sed -i 's/[.]toOffset()//g' git ls-files -z | xargs -0 sed -i 's/[.]toPoint()//g' git ls-files -z | xargs -0 sed -i 's/\bshow Point, /show /g' git ls-files -z | xargs -0 sed -i 's/\bshow Point;/show Offset;/g' * Mechanical changes - dartdocs I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\ba \[Point\]/an [Offset]/g' git ls-files -z | xargs -0 sed -i 's/\[Point\]/[Offset]/g' * Further improvements and a test * Fix minor errors from rebasing... * Roll engine
-
- 16 Nov, 2016 1 commit
-
-
Adam Barth authored
-
- 30 Sep, 2016 1 commit
-
-
Adam Barth authored
Now dart:ui does the decoding of the pointer data itself, which means we don't need to do it in the framework.
-
- 17 May, 2016 1 commit
-
-
Adam Barth authored
Also, add some missing docs to http.dart and widgets.dart.
-
- 14 Mar, 2016 1 commit
-
-
Hixie authored
-
- 05 Feb, 2016 1 commit
-
-
Adam Barth authored
-
- 05 Dec, 2015 2 commits
-
-
Ian Hickson authored
-
Ian Hickson authored
Instead of PointerInputEvent having a "type" field, we now have a different class for each pointer type. This has ripple effects throughout the system. I also did code cleanup in affected files while I was there.
-