using System.ComponentModel; using System.Windows.Forms; namespace BizHawk.WinForms.Controls { /// Static members are dummies, referenced only in docs in order to centralise them. internal static class Docs { /// Inherits . /// Naming convention for control types /// /// public const bool Button = true; /// Inherits /. /// Naming convention for control types /// /// public const bool CheckBoxOrRadioButton = true; /// Inherits . /// Naming convention for control types /// /// public const bool GroupBox = true; /// Inherits /. /// Naming convention for control types /// /// /// /// /// public const bool LabelOrLinkLabel = true; /// Inherits . Only Sz* variants are available. /// Naming convention for control types /// public const bool NUD = true; /// /// Inherits . /// is locked to and is locked to . /// is locked to / for rows/columns, respectively. /// /// Naming convention for control types /// /// public const bool RowsOrColsFLP = true; /// /// Inherits . /// is locked to and is locked to . /// is locked to / for a single row/column, respectively. /// /// Naming convention for control types /// /// /// /// /// /// public const bool SingleRowOrColFLP = true; /// Inherits . /// Naming convention for control types /// public const bool TabPage = true; /// Inherits . Only Sz* variants are available. /// Naming convention for control types /// public const bool TextBox = true; /// /// This project has some naming conventions in regards to type names. /// /// Loc* are positionable; instances should set . The intention is for controls without Loc to be used in FLPs. /// Sz* are resizable; instances should set . is always set for you, with or without this prefix. /// These combine as expected. A type name without any prefix is the most restrictive, having many properties pre-set (which is a double-edged sword as they can't be changed). /// /// In addition, properties are hidden in the Designer (with ) when they are read-only and their value is clear from the type name. /// public const bool TypeNamePrefix = true; } }