From ae4fb0ca7c0ca9091aed3add162e29a31a967951 Mon Sep 17 00:00:00 2001 From: Michael Goderbauer Date: Wed, 3 Jan 2024 15:01:57 -0800 Subject: [PATCH] fix typo and reflow (#140925) Fixes "differenet" => "different" and reflows the doc to 80 char line length. --- .../src/gestures/pointer_signal_resolver.dart | 24 ++++++++++--------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/packages/flutter/lib/src/gestures/pointer_signal_resolver.dart b/packages/flutter/lib/src/gestures/pointer_signal_resolver.dart index e2e4ce24273..2e4b6709d33 100644 --- a/packages/flutter/lib/src/gestures/pointer_signal_resolver.dart +++ b/packages/flutter/lib/src/gestures/pointer_signal_resolver.dart @@ -61,21 +61,23 @@ class PointerSignalResolver { /// Registers interest in handling [event]. /// - /// This method may be called multiple times (typically from different parts of the - /// widget hierarchy) for the same `event`, with differenet `callback`s, as the event - /// is being dispatched across the tree. Once the dispatching is complete, the - /// [GestureBinding] calls [resolve], and the first registered callback is called. + /// This method may be called multiple times (typically from different parts + /// of the widget hierarchy) for the same `event`, with different `callback`s, + /// as the event is being dispatched across the tree. Once the dispatching is + /// complete, the [GestureBinding] calls [resolve], and the first registered + /// callback is called. /// /// The `callback` is invoked with one argument, the `event`. /// - /// Once the [register] method has been called with a particular `event`, it must - /// not be called for other `event`s until after [resolve] has been called. Only one - /// event disambiguation can be in flight at a time. In normal use this is achieved - /// by only registering callbacks for an event as it is actively being dispatched - /// (for example, in [Listener.onPointerSignal]). + /// Once the [register] method has been called with a particular `event`, it + /// must not be called for other `event`s until after [resolve] has been + /// called. Only one event disambiguation can be in flight at a time. In + /// normal use this is achieved by only registering callbacks for an event as + /// it is actively being dispatched (for example, in + /// [Listener.onPointerSignal]). /// - /// See the documentation for the [PointerSignalResolver] class for an example of - /// using this method. + /// See the documentation for the [PointerSignalResolver] class for an example + /// of using this method. void register(PointerSignalEvent event, PointerSignalResolvedCallback callback) { assert(_currentEvent == null || _isSameEvent(_currentEvent!, event)); if (_firstRegisteredCallback != null) {