Flutter Engine
The Flutter Engine
Loading...
Searching...
No Matches
Instance Methods | List of all members
<FlutterTextureRegistry> Protocol Reference

#include <FlutterTexture.h>

Inheritance diagram for <FlutterTextureRegistry>:
FlutterEngine FlutterTextureRegistrar FlutterTextureRegistryRelay FlutterViewController FlutterEnginePartialMock FlutterEngineSpy FlutterHeadlessDartRunner MockableFlutterEngine AccessibilityBridgeTestViewController MouseEventFlutterViewController NoStatusBarFlutterViewController ShareViewController TextInputTestViewController

Instance Methods

(int64_t) - registerTexture:
 
(void) - textureFrameAvailable:
 
(void) - unregisterTexture:
 

Detailed Description

A collection of registered FlutterTexture's.

Definition at line 45 of file FlutterTexture.h.

Method Documentation

◆ registerTexture:

- (int64_t) registerTexture: (NSObject< FlutterTexture > *)  texture

Registers a FlutterTexture for usage in Flutter and returns an id that can be used to reference that texture when calling into Flutter with channels. Textures must be registered on the platform thread. On success returns the pointer to the registered texture, else returns 0.

Reimplemented in FlutterEngine, FlutterTextureRegistryRelay, and FlutterViewController.

◆ textureFrameAvailable:

- (void) textureFrameAvailable: (int64_t)  textureId

Notifies Flutter that the content of the previously registered texture has been updated.

This will trigger a call to -[FlutterTexture copyPixelBuffer] on the raster thread.

Reimplemented in FlutterEngine, FlutterTextureRegistryRelay, FlutterViewController, and FlutterTextureRegistrar.

◆ unregisterTexture:

- (void) unregisterTexture: (int64_t)  textureId

Unregisters a FlutterTexture that has previously regeistered with registerTexture:. Textures must be unregistered on the platform thread.

Parameters
textureIdThe result that was previously returned from registerTexture:.

Reimplemented in FlutterEngine, FlutterTextureRegistryRelay, FlutterViewController, and FlutterTextureRegistrar.


The documentation for this protocol was generated from the following file: