<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."/>
@ -50,18 +68,11 @@
<itemvalue="Path to a directory where the application may place data that is user-generated, or that cannot otherwise be recreated by your application. Consider using another path, such as [getApplicationSupportDirectory], [getApplicationCacheDirectory], or [getExternalStorageDirectory], if the data is not user-generated. Example implementations: - `NSDocumentDirectory` on iOS and macOS. - The Flutter engine's `PathUtils.getDataDirectory` API on Android. Throws a [MissingPlatformDirectoryException] if the system is unable to provide the directory."/>
<itemvalue="station location status locate fail"/>
<itemvalue="Arguments for the call. Consider using arguments() for cases where a particular run-time type is expected. Consider using argument(String) when that run-time type is Map or JSONObject."/>
<itemvalue="the arguments, a value supported by the channel's message codec. Possibly, null."/>
<itemvalue="Returns the modular multiplicative inverse of this integer modulo [modulus]. The [modulus] must be positive. It is an error if no modular inverse exists."/>
<itemvalue="The mode of the file system object. Permissions are encoded in the lower 16 bits of this number, and can be decoded using the [modeString] getter."/>
<itemvalue="Starts a process and runs it non-interactively to completion. The process run is [executable] with the specified [arguments]."/>
<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="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."/>
debuggerx
2 months ago