The base class for all other GUI widgets This forms the basis of any visual widget in fpGUI . Sets the position and size of the component . It also fires the Resize message. If you are setting up a component like a button on a form, you don't really want the resize event to fire for the button, before the form is displayed (visible). In that case, rather use the components Top, Left, Width and Height properties. TfpgWindowBase.UpdateWindowPosition If assigned, then this widget is being editing in the Form Designer An alias for Owner Unlike Delphi or Lazarus, fpGUI treats Owner and Parent as the same thing. Owner or Parent manages the life of children, and the parent/child hierarchy defines the visual aspect as well. Can this widget manage child widgets This is mainly used in fpGUI UI Designer, to know if you can drop a widget inside another widget. This determines if the widget is allowed to received keyboard focus . No focus rectangle will be drawn, even if the user clicks this component. Allows the component to resize or reposition based on its Parent.

By default Anchors are set to Top Left.

Anchoring only takes affect after the component is visible on the screen (when the component has a window handle assigned). So if you create a Button in the constructor and set its Anchor property to Bottom/Right, and then set the size of the Form, the Button will not be repositioned.

This is by design. fpGUI allows you to setup a window layout without triggering unnecesary events as you set property values for each widget. Only when csLoading is not in ComponentState, then anchoring events will be triggered. This allows the developer or the fpGUI UI Designer to setup a window layout undisturbed.

 Occurs after the component processed the mouse button press event . By default this method also triggers the OnClick event, but this behaviour can be overridden by descendant components. Display context-sensitive help

InvokeHelp is called automatically when the user presses the application help key (normally F1) while the widget has the focus. If a help topic is defined for this widget (using HelpContext or HelpKeyword, depending on the value of HelpType), then InvokeHelp displays the topic by calling the KeywordHelp or ContextHelp method of the fpgApplication object. If no help topic is defined, then InvokeHelp attempts to call InvokeHelp for its parent. This allows a container widget to specify a default help topic for its children.

 TfpgApplication.HelpFile