.. _doxcsid-interface_p1_1_1_image_sdk_1_1_i_int_ptr_providable:

IIntPtrProvidable Interface
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Definition
^^^^^^^^^^

*Namespace:* ``P1.ImageSdk``

Interface for a IDisposable object that creates and destroys a GCHandle to an IntPtr :ref:`More...<csdetails-interface_p1_1_1_image_sdk_1_1_i_int_ptr_providable>`

.. ref-code-block:: csharp
	:class: doxyrest-overview-code-block

	public interface IIntPtrProvidable :  IDisposable


.. _csdetails-interface_p1_1_1_image_sdk_1_1_i_int_ptr_providable:

Remarks
^^^^^^^

Interface for a IDisposable object that creates and destroys a GCHandle to an IntPtr

In order to make a GCHandle's IntPtr as short lived as possible, objects of this type will create the IntPtr when you receive the IntPtrProvidable and destroy the handle when you dispose your IntPtrProvidable - which you should do ASAP.

:ref:`BitmapImage <doxcsid-class_p1_1_1_image_sdk_1_1_bitmap_image>` and :ref:`HugeBitmapImage <doxcsid-class_p1_1_1_image_sdk_1_1_huge_bitmap_image>` both can provide IntPtrProvidable to their data, but :ref:`HugeBitmapImage <doxcsid-class_p1_1_1_image_sdk_1_1_huge_bitmap_image>` holds its pixel data in unmanaged memory. Still, it uses this interface for compatibility.


Properties
^^^^^^^^^^

.. toctree::
	:hidden:

	Ptr <property_P1_ImageSdk_IIntPtrProvidable_Ptr.rst>

.. list-table::
	:widths: 30 70

	*
		- :ref:`Ptr <doxcsid-interface_p1_1_1_image_sdk_1_1_i_int_ptr_providable_1af289d536ee6fa51b62232cde172084c4>`
		- Returns the IntPtr that is handled by this provider