Support.CursorToIPicture(Cursor) Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Caution
Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862
Returns an OLE IPicture object that corresponds to the specified Cursor.
public:
static System::Object ^ CursorToIPicture(System::Windows::Forms::Cursor ^ curs);public static object CursorToIPicture (System.Windows.Forms.Cursor curs);[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public static object CursorToIPicture (System.Windows.Forms.Cursor curs);static member CursorToIPicture : System.Windows.Forms.Cursor -> obj[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
static member CursorToIPicture : System.Windows.Forms.Cursor -> objPublic Function CursorToIPicture (curs As Cursor) As ObjectParameters
Returns
An Object that represents the OLE IPicture object.
- Attributes
Remarks
In Visual Basic 6.0, the MouseIcon property of a form or control could be used to load a custom MousePointer (cursor). In some cases, the image for the MouseIcon was stored as a stdOle.IPicture; this function is used by the upgrade tool to convert a Cursor to a stdOle.IPicture.
To convert a Cursor in Visual Basic, use the GetIPictureFromCursor method of the AxHost class.
Note
Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic 2008. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.
