getBytePointer
TypeScriptget getBytePointer(): (((arg0: (SDKHandle) | null) => Promise<(SDKHandle) | null>)) | nullSwift declarationvar getBytePointer: CGDataProviderGetBytePointerCallback?struct · SDK 27.1
struct CGDataProviderDirectCallbacksget getBytePointer(): (((arg0: (SDKHandle) | null) => Promise<(SDKHandle) | null>)) | nullSwift declarationvar getBytePointer: CGDataProviderGetBytePointerCallback?get getBytesAtPosition(): (((arg0: (SDKHandle) | null, arg1: SDKHandle, arg2: SDKHandle, arg3: number) => Promise<number>)) | nullSwift declarationvar getBytesAtPosition: CGDataProviderGetBytesAtPositionCallback?get releaseBytePointer(): (((arg0: (SDKHandle) | null, arg1: SDKHandle) => Promise<void>)) | nullSwift declarationvar releaseBytePointer: CGDataProviderReleaseBytePointerCallback?get releaseInfo(): (((arg0: (SDKHandle) | null) => Promise<void>)) | nullSwift declarationvar releaseInfo: CGDataProviderReleaseInfoCallback?get version(): numberSwift declarationvar version: UInt32set version(value: number)Swift declarationvar version: UInt32static init(): CGDataProviderDirectCallbacksSwift declarationinit()5 declarations were excluded from these bindings. Each reason comes from the generator or the iOS SDK compiler.
CGDataProviderDirectCallbacks.init(version:getBytePointer:releaseBytePointer:getBytesAtPosition:releaseInfo:)
callback cannot propagate synchronous failure
CGDataProviderDirectCallbacks.getBytePointer
closure property answers its caller
CGDataProviderDirectCallbacks.releaseBytePointer
The iOS SDK compiler rejected this binding: a C function pointer can only be formed from a reference to a 'func' or a literal closure
CGDataProviderDirectCallbacks.getBytesAtPosition
closure property answers its caller
CGDataProviderDirectCallbacks.releaseInfo
The iOS SDK compiler rejected this binding: a C function pointer can only be formed from a reference to a 'func' or a literal closure