<itemvalue="Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically, Expanded widgets are placed directly inside Flex widgets. The offending Expanded is currently placed inside a Opacity widget."/>
<itemvalue="Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically, Expanded widgets are placed directly inside Flex widgets. The offending Expanded is currently placed inside a Opacity widget."/>
<itemvalue="Draws a shadow for a [Path] representing the given material elevation. The `transparentOccluder` argument should be true if the occluding object is not opaque. The arguments must not be null."/>
<itemvalue="Draws a shadow for a [Path] representing the given material elevation. The `transparentOccluder` argument should be true if the occluding object is not opaque. The arguments must not be null."/>
<itemvalue="A pointer that has triggered a long-press with a primary button has stopped contacting the screen."/>
<itemvalue="A pointer that has triggered a long-press with a primary button has stopped contacting the screen."/>
@ -56,7 +57,6 @@
<itemvalue="A named channel for communicating with platform plugins using event streams. Stream setup requests are encoded into binary before being sent, and binary events and errors received are decoded into Dart values. The [MethodCodec] used must be compatible with the one used by the platform plugin. This can be achieved by creating an [EventChannel] counterpart of this channel on the platform side. The Dart type of events sent and received is `dynamic`, but only values supported by the specified [MethodCodec] can be used. The logical identity of the channel is given by its name. Identically named channels will interfere with each other's communication. See: <https:flutter.devtoplatform-channels>"/>
<itemvalue="A named channel for communicating with platform plugins using event streams. Stream setup requests are encoded into binary before being sent, and binary events and errors received are decoded into Dart values. The [MethodCodec] used must be compatible with the one used by the platform plugin. This can be achieved by creating an [EventChannel] counterpart of this channel on the platform side. The Dart type of events sent and received is `dynamic`, but only values supported by the specified [MethodCodec] can be used. The logical identity of the channel is given by its name. Identically named channels will interfere with each other's communication. See: <https:flutter.devtoplatform-channels>"/>
<itemvalue="Creates an [EventChannel] with the specified [name]. The [codec] used will be [StandardMethodCodec], unless otherwise specified. Neither [name] nor [codec] may be null. The default [ServicesBinding.defaultBinaryMessenger] instance is used if [binaryMessenger] is null."/>
<itemvalue="Creates an [EventChannel] with the specified [name]. The [codec] used will be [StandardMethodCodec], unless otherwise specified. Neither [name] nor [codec] may be null. The default [ServicesBinding.defaultBinaryMessenger] instance is used if [binaryMessenger] is null."/>
<itemvalue="Handler of stream setup and teardown requests. Implementations must be prepared to accept sequences of alternating calls to onListen(Object, EventChannel. EventSink) and onCancel(Object). Implementations should ideally consume no resources when the last such call is not onListen. In typical situations, this means that the implementation should register itself with platform-specific event sources onListen and deregister again onCancel."/>
<itemvalue="Handler of stream setup and teardown requests. Implementations must be prepared to accept sequences of alternating calls to onListen(Object, EventChannel. EventSink) and onCancel(Object). Implementations should ideally consume no resources when the last such call is not onListen. In typical situations, this means that the implementation should register itself with platform-specific event sources onListen and deregister again onCancel."/>
<itemvalue="Event callback. Supports dual use: Producers of events to be sent to Flutter act as clients of this interface for sending events. Consumers of events sent from Flutter implement this interface for handling received events (the latter facility has not been implemented yet)."/>