~ubuntu-branches/ubuntu/trusty/monodevelop/trusty-proposed

<para>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 you invoke the constructor that takes the NSObjectFlag.Empty you taking advatnage 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 you.</para>

<para>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.</para>

<para>It is your responsability to completely initialize the object if you chain up using the NSObjectFlag.Empty path.</para>

<para>In general, if your constructors invokes the NSObjectFlag.Empty base implementation, then it should be calling an Objective-C init method. If this is not the case, you should instead chain to the proper constructor in your class. </para>

<para>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:</para>

<para>This constructor should be called by derived classes when they are initialized using an [Export] attribute. The argument value is ignore, typically the chaining would look like this:</para>

// The NSObjectFlag merely allocates the object and registers the

// C# class with the Objective-C runtime if necessary, but no actual

// initXxx method is invoked, that is done later in the constructor

// This is taken from MonoMac's source code:

[Export ("initWithFrame:")]

public UIView (System.Drawing.RectangleF frame) : base (NSObjectFlag.Empty)

{

// Invoke the init method now.

var initWithFrame = new Selector ("initWithFrame:").Handle;

if (IsDirectBinding)

Handle = MonoMac.ObjCRuntime.Messaging.IntPtr_objc_msgSend_RectangleF (this.Handle, initWithFrame, frame);

else

Handle = MonoMac.ObjCRuntime.Messaging.IntPtr_objc_msgSendSuper_RectangleF (this.SuperHandle, initWithFrame, frame);

}

public class MyClass : BaseClass {

[Export ("initWithFoo:")]

public MyClass (string foo) : base (NSObjectFlag.Empty)

{

...

}

100

</code>

101

</example>

102

</remarks>

109

105

110

106

111

107

</AssemblyInfo>

108

109

110

<AttributeName>System.ComponentModel.EditorBrowsable(System.ComponentModel.EditorBrowsableState.Advanced)</AttributeName>

111

</Attribute>

112

</Attributes>

112

113

113

114

114

115

</Parameters>

327

328

328

329

<para>If set to <see langword="true" />, the method is invoked directly and will dispose manage and unmanaged resources; If set to <see langword="false" /> the method is being called by the garbage collector finalizer and should only release unmanaged resources.</para>

329

330

</param>

330

<summary>Releases the resourced used by the NSCursor object.</summary>

331

<summary>Releases the resources used by the NSCursor object.</summary>

331

332

332

333

<para>This Dispose method releases the resources used by the NSCursor class.</para>

333

334

<para>This method is called by both the Dispose() method and the object finalizer (Finalize). When invoked by the Dispose method, the parameter disposting <paramref name="disposing" /> is set to <see langword="true" /> and any managed object references that this object holds are also disposed or released; when invoked by the object finalizer, on the finalizer thread the value is set to <see langword="false" />. </para>

Older »