- 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
-
- 27 Aug, 2019 1 commit
-
-
Tong Mu authored
Add "OneSequenceRecognizer.resolvePointer". Fix DragGestureRecognizer crash on multiple pointers (#39017) * Add drag tests * Add resolvePointer * Correct monodrag implementation * Fix some addTearDown
-
- 06 Jun, 2019 2 commits
-
-
Michael Goderbauer authored
-
Michael Goderbauer 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
-
- 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.
-
- 25 May, 2019 2 commits
-
-
Chris Bracken authored
Updates documentation and non-public API to use American spellings for consistency with the rest of the codebase. No changes to behaviour... other than how it's spelt.
-
Chris Bracken authored
Corects a bnuch of typeos throuhgout teh Fluter codebsae. Made use of the `misspell` tool: https://github.com/client9/misspell
-
- 20 May, 2019 1 commit
-
- 14 May, 2019 3 commits
-
-
Mouad Debbar authored
-
Mouad Debbar authored
This reverts commit 18ca3754.
-
Mouad Debbar authored
-
- 09 May, 2019 2 commits
-
-
Michael Goderbauer authored
-
Greg Spencer authored
This changes Listener to trigger enter/move/exit in all Listeners below the pointer, not just the leaf region (the first region hit). This is because we need to allow listeners to be nested so that, say, a widget that handles changing color on hover, but also is wrapped in a Tooltip (that handles hover) can trigger both actions, not just one. To that end, I added a findAll to Layer, similar to the existing find method that was previously used. It returns an iterator over annotated layers which match the given data type. Since the findAll is implemented as returning an Iterable (and is sync*), I re-implemented the find routines as just returning the first result from findAll, since that should be just as efficient, and would then prevent duplication in the implementation.
-
- 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.
-
- 11 Apr, 2019 1 commit
-
-
Emily Fortuna authored
* Allow mouse hover to only respond to some mouse events but not all.
-
- 05 Apr, 2019 1 commit
-
-
Tong Mu authored
* Correctly synthesise buttons, and add tests
-
- 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.
-
- 09 Mar, 2019 1 commit
-
-
Alexandre Ardhuin authored
-