MDLMesh Constructors

[Foundation.Export("init")]
[ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)]
public MDLMesh();

Attributes

ExportAttribute BindingImplAttribute

[ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)]
protected MDLMesh(Foundation.NSObjectFlag t);

[<ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)>]
new ModelIO.MDLMesh : Foundation.NSObjectFlag -> ModelIO.MDLMesh

Parameters

Attributes

BindingImplAttribute

Remarks

This constructor should be called by derived classes when they completely construct the object in managed code and merely want the runtime to allocate and initialize the NSObject. This is required to implement the two-step initialization process that Objective-C uses, the first step is to perform the object allocation, the second step is to initialize the object. When developers invoke this constructor, they take advantage of a direct path that goes all the way up to NSObject to merely allocate the object's memory and bind the Objective-C and C# objects together. The actual initialization of the object is up to the developer.

This constructor is typically used by the binding generator to allocate the object, but prevent the actual initialization to take place. Once the allocation has taken place, the constructor has to initialize the object. With constructors generated by the binding generator this means that it manually invokes one of the "init" methods to initialize the object.

It is the developer's responsibility to completely initialize the object if they chain up using this constructor chain.

In general, if the developer's constructor invokes the corresponding base implementation, then it should also call an Objective-C init method. If this is not the case, developers should instead chain to the proper constructor in their class.

The argument value is ignored and merely ensures that the only code that is executed is the construction phase is the basic NSObject allocation and runtime type registration. Typically the chaining would look like this:

//
// The NSObjectFlag constructor merely allocates the object and registers the C# class with the Objective-C runtime if necessary.
// No actual initXxx method is invoked, that is done later in the constructor
//
// This is taken from the iOS SDK's source code for the UIView class:
//
[Export ("initWithFrame:")]
public UIView (CGRect frame) : base (NSObjectFlag.Empty)
{
    // Invoke the init method now.
    var initWithFrame = new Selector ("initWithFrame:").Handle;
    if (IsDirectBinding) {
        Handle = ObjCRuntime.Messaging.IntPtr_objc_msgSend_CGRect (this.Handle, initWithFrame, frame);
    } else {
        Handle = ObjCRuntime.Messaging.IntPtr_objc_msgSendSuper_CGRect (this.SuperHandle, initWithFrame, frame);
    }
}

[Foundation.Export("initWithBufferAllocator:")]
[ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)]
public MDLMesh(ModelIO.IMDLMeshBufferAllocator? bufferAllocator);

[<Foundation.Export("initWithBufferAllocator:")>]
[<ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)>]
new ModelIO.MDLMesh : ModelIO.IMDLMeshBufferAllocator -> ModelIO.MDLMesh

Parameters

Attributes

ExportAttribute BindingImplAttribute

[ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)]
protected internal MDLMesh(ObjCRuntime.NativeHandle handle);

[<ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)>]
new ModelIO.MDLMesh : ObjCRuntime.NativeHandle -> ModelIO.MDLMesh

Parameters

Attributes

BindingImplAttribute

Remarks

This constructor is invoked by the runtime infrastructure (GetNSObject(IntPtr)) to create a new managed representation for a pointer to an unmanaged Objective-C object. Developers should not invoke this method directly, instead they should call GetNSObject(IntPtr) as it will prevent two instances of a managed object pointing to the same native object.

[Foundation.Export("initWithVertexBuffer:vertexCount:descriptor:submeshes:")]
[ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)]
public MDLMesh(ModelIO.IMDLMeshBuffer vertexBuffer, UIntPtr vertexCount, ModelIO.MDLVertexDescriptor descriptor, ModelIO.MDLSubmesh[] submeshes);

[<Foundation.Export("initWithVertexBuffer:vertexCount:descriptor:submeshes:")>]
[<ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)>]
new ModelIO.MDLMesh : ModelIO.IMDLMeshBuffer * unativeint * ModelIO.MDLVertexDescriptor * ModelIO.MDLSubmesh[] -> ModelIO.MDLMesh

Parameters

Attributes

ExportAttribute BindingImplAttribute

[Foundation.Export("initWithVertexBuffers:vertexCount:descriptor:submeshes:")]
[ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)]
public MDLMesh(ModelIO.IMDLMeshBuffer[] vertexBuffers, UIntPtr vertexCount, ModelIO.MDLVertexDescriptor descriptor, ModelIO.MDLSubmesh[] submeshes);

[<Foundation.Export("initWithVertexBuffers:vertexCount:descriptor:submeshes:")>]
[<ObjCRuntime.BindingImpl(ObjCRuntime.BindingImplOptions.GeneratedCode | ObjCRuntime.BindingImplOptions.Optimizable)>]
new ModelIO.MDLMesh : ModelIO.IMDLMeshBuffer[] * unativeint * ModelIO.MDLVertexDescriptor * ModelIO.MDLSubmesh[] -> ModelIO.MDLMesh

Parameters

Attributes

ExportAttribute BindingImplAttribute