Ultimate Page Control Suite™ Win32 | Delphi™ | C++Builder™; C.01. INTRODUCTION TO THE TUTORIAL

Paging-related members of UPC™ modules are exposed by TADVANCE_PMInterface subcomponents which are uniformly named after the internalized module — "PM1_Main", "PM2_ToolsTop", "PM3_RelTop", "PM4_RelBot", "PM5_Toolsbot", and "PM6_Status." The following expressions therefore would call the AddPageAt() function of any module's main paging region. Your code will follow this pattern:

BASIC ISSUES

Dropping controls:
As with conventional page controls, visual controls can only be dropped on page classes intended to accept visual controls from the IDE.
- You must add and focus pages before you can drop controls onto *only* a focused page of an appropriate class.
- Paged Toolbars™ are populated by editing their tool collection, and will not accept controls from the IDE.
- Legitimate dropping targets therefore are only TADVANCE_Page descendants which do not belong to TADVANCE_Page_PagedTools. These are all pages but those of PagedToolbar modules.
Where to find relevant documentation:
To consolidate information, TADVANCE class descendants are documented with their base class.
- This means that you can find related information of class branches together.
- Understand however that base classes will not necessarily possess all documented members.
- VCL members are documented by the IDE.
Selecting modules, or parts of a module:
To select a page module, click its main FocusControl.
- Although you can select FocusControls of embedded composite modules because the Delphi and C++Builder IDEs provide no way of preventing selection, you should only select the main focus control of a module or pages.
- Invoke the component editor for the root module by right-clicking its main FocusControl.