A named channel for communicating with platform plugins using asynchronous method calls.
Method calls are encoded into binary before being sent, and binary results 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 a method channel counterpart of this channel on the platform side. The Dart type of arguments and results is dynamic
, but only values supported by the specified MethodCodec can be used. The use of unsupported values should be considered programming errors, and will result in exceptions being thrown. The null value is supported for all codecs.
The logical identity of the channel is given by its name. Identically named channels will interfere with each other's communication.
All MethodChannels provided by the Flutter framework guarantee FIFO ordering. Applications can assume method calls sent via a built-in MethodChannel are received by the platform plugins in the same order as they're sent.
See: flutter.dev/to/platform-channels/
name
.
const
no setter
final
no setterinherited
final
no setterinherited
Available on MethodChannel, provided by the TestMethodChannelExtension extension
Shim for TestDefaultBinaryMessenger.checkMockMessageHandler.method
on this channel with the specified arguments
.
inherited
Available on MethodChannel, provided by the TestMethodChannelExtension extension
Shim for TestDefaultBinaryMessenger.setMockMethodCallHandler.inherited
inherited
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4