ScaleMode Enum
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
Provides constants for compatibility with the ScaleMode
constants in Visual Basic 6.0.
public enum class ScaleMode
public enum ScaleMode
[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public enum ScaleMode
type ScaleMode =
[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
type ScaleMode =
Public Enum ScaleMode
- Inheritance
- Attributes
Fields
Name | Value | Description |
---|---|---|
Points | 2 | Equivalent to the Visual Basic 6.0 constant |
Characters | 4 | Equivalent to the Visual Basic 6.0 constant |
Inches | 5 | Equivalent to the Visual Basic 6.0 constant |
Millimeters | 6 | Equivalent to the Visual Basic 6.0 constant |
Centimeters | 7 | Equivalent to the Visual Basic 6.0 constant |
Himetric | 8 | Equivalent to the Visual Basic 6.0 constant |
Remarks
In Visual Basic 6.0, ScaleMode
constants were used to represent various units of measurement for the ScaleMode
property. In Visual Basic, the ScaleMode
property is no longer supported, and these constants are no longer necessary. These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.
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. 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.