Support.FontChangeStrikeout(Font, Boolean) 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
Changes the Strikeout style bit for a font.
public:
static System::Drawing::Font ^ FontChangeStrikeout(System::Drawing::Font ^ CurrentFont, bool Strikeout);
public static System.Drawing.Font FontChangeStrikeout (System.Drawing.Font CurrentFont, bool Strikeout);
[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public static System.Drawing.Font FontChangeStrikeout (System.Drawing.Font CurrentFont, bool Strikeout);
static member FontChangeStrikeout : System.Drawing.Font * bool -> System.Drawing.Font
[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
static member FontChangeStrikeout : System.Drawing.Font * bool -> System.Drawing.Font
Public Function FontChangeStrikeout (CurrentFont As Font, Strikeout As Boolean) As Font
Parameters
Returns
A Font with the new style applied.
- Attributes
Remarks
In Visual Basic 6.0, font styles were applied by setting properties; in Visual Basic font styles are applied by using a FontStyle enumeration. This function is used by the upgrade tools to translate the Visual Basic 6.0 properties to the new enumerations.
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.