Control Constructor (Typed) | |
Construct a control.
Namespace:
XSharp.VO.SDK
Assembly:
XSharp.VOGUIClasses (in XSharp.VOGUIClasses.dll) Version: 2.19
Syntax CONSTRUCTOR(
oOwner,
xID,
oPoint,
oDimension,
cRegClass,
kStyle,
lDataAware
) CLIPPER
[ClipperCallingConventionAttribute(new string[] { ... })]
public Control(
Usual oOwner = default,
Usual xID = default,
Usual oPoint = default,
Usual oDimension = default,
Usual cRegClass = default,
Usual kStyle = default,
Usual lDataAware = default
)
Request Example
View SourceParameters
- oOwner (Optional)
- Type: Usual
The window that owns the control. - xID (Optional)
- Type: Usual
The unique ID of the control (between 1 and 8000). - oPoint (Optional)
- Type: Usual
The origin of the control in canvas coordinates. - oDimension (Optional)
- Type: Usual
The dimension of the control in canvas coordinates. - cRegClass (Optional)
- Type: Usual
String representing the control class (for example, 'Edit', 'ListBox', etc.) - kStyle (Optional)
- Type: Usual
Constant representing the style of the control, specified either by a X# style constant or a Windows API style constant.
Styles can be combined using the _Or() operator.
- lDataAware (Optional)
- Type: Usual
Logical value indicating whether the control is data-aware (TRUE) or not (FALSE). The default is FALSE.
Remarks Tip |
---|
Consult your Microsoft Win32 Software Development Kit documentation for detailed information about a particular Windows API constant. |
Controls are created in one of two ways: dynamically or from a compiled dialog resource. Dynamic creation, which requires that size and position be specified as instantiation parameters, can be used on any type of window. A compiled dialog resource (which specifies both size and location of the control) can be used only with data windows and dialog windows.
Additionally, the default state when a control is created depends on the way you placed the control:
With dynamic creation, the control remains invisible until you invoke Control:Show().
This allows the program to set up the control correctly (with the correct size, position, and any other parameters), while avoiding the "visual noise" of changing controls.
With resource-bound instantiation, the control is automatically shown, without requiring a call to Control:Show().
See Also