A minimum desktop workarea of 1280 x 1024 and 32-bit Windows 2000® or XP® are required for these C++ and Delphi demos.

  • Bundled libraries unzip together into one directory, and must remain in the executable directory to run either demo.
  • No setup application is involved, and your system registry is untouched.
  • Run either executable, referring to this page for documentation.
  • CLICK HERE to download zippedUPCBDS2006Win32DEMOS.zip (~1,500 Kb), which includes both Delphi™ and C++ Builder™ executables.
    Last updated, .
  • Please note that mail applications of non-Windows operating systems can corrupt files. To avoid problems, download directly from this page to the Windows target system.
  • Other sites have been distributing out of date UPC™ Demos. Please maintain up-to-date distributables, or instead provide links to this page. Product description code can be copied to your site source files with the following copy-to-clipboard tool.


    Copy code to clipboard (JavaScript/IE).


Page 1 of the control side.

The demos dynamically propagate up to 500 main DataMaster pages, and support an additional population of nearly 100 composite and control side pages in 7 paging regions containing several hundred tools dynamically wired to handlers.


    Controls 2 and 3 are automatically enabled.

  2. Select the number of main pages to generate.

    Page 1 will automatically close and focus Page 2. In the Demo source, notice this is accomplished simply by enabling CanFocus for pages 2..5 and disabling CanFocus for page 1. By letting security behavior control focusing, it is not necessary to call a navigation method.


The related articles, Goals of the Paged, Multiple Workspace (PMW) Application Development Model, and How to Build Superior Paged, Multiple Workspace (PMW) Applications, explain how developers may build PMW applications which might process relatively tremendous workspace populations from smaller code bases than drive conventional Single Workspace (SW) applications.

In the UPC™ infrastructure itself, resource consumption is minimized largely by exhaustive consolidation. UPC™ resource footprints are so light that developers can select modules on the basis of eventual needs — simply hiding unused regions, or using paged regions statically, with virtually no resource penalty.

How efficient are UPC™ footprints?

Despite six paged regions, navigation and sizing support, secure and general navigation, spatial management, wrapping support for 3 toolbar regions, 38 24-bit glyphs in the MasterToolbar™, and 6 FocusButton™ glyphs, dropping a PM04_DataMaster module onto the demo application raises the footprint a mere 24 Kb. A conventional tabbed page control raises the footprint 17 Kb, merely to paginate a single region.


Populated TADVANCE_PM04_DataMasterUPA.

Populated TADVANCE_PM04_DataMasterUPA.

Top to bottom, regions of TADVANCE_PM04_DataMasterUPA are:

  1. Main FocusControl™

    The main FocusControl (top) hosts the FocusButton (left) and managed AuxTools collection (right). Left-clicking a FocusButton invokes the NavigationWindow. Right-clicking invokes the SizingWindow, if sizing events are assigned to the PMInterface. Left-aligned FocusControls of the further paged regions are recognized by their drop-down glyphs.

  2. LogoPanel™

    LogoPanel™s symbolize module purposes, and are automatically replicated in the NavigationWindow.

  3. MasterToolbar™

    The MasterToolbar™ negotiates and processes interfaced tables which are automatically focused by page navigation. See Deploying the MasterToolbar™ for any RDBMS API Objects, and Handling the Integrity of an Application's Connection to its Server, for related background.

  4. Top Paged Toolbar™

    Paged Toolbar™ regions host paged (interchangeable) or static (fixed) toolbars with configurable wrapping behavior. Page Toolbar properties globally maintain dimensions, order, glyph layout, margins, spacing, and caption visibility of the managed Tools collection. Demo toolbars are marked by square glyphs.

  5. Top Paged Related Controls™

    Related Controls™ regions host paged or static controls which usually process content of the Main pages, and which avoid obscuring processed content in the manner of modal dialogs. See Goals of the Paged, Multiple Workspace (PMW) Application Development Model for further information.

  6. Main Paged Region

    The main paged region of the DataMaster™ module typically interfaces database tables processed by the MasterToolbar™.

  7. Bottom Paged Related Controls™

    Usually processes specialized content located in the lower regions of Main pages.

  8. Bottom Paged Toolbar™

    Usually processes specialized content located in the lower regions of Main pages.

  9. Paged Status™

    Paged Status™ regions host paged or static status controls.

For a reasonable distributable, no database functionality is provided. Main, Related, and Status pages are simply populated with labels distinguishing each page. Status page labels are created by descending and propagating a custom status page class. Support topics illustrate how to deploy custom page classes in minutes.


Page 2.

Page 2 demonstrates how PageGroup membership is handled by page propagation methods. Effects are observed in the main FocusButton and NavigationWindow. See AddPageAt(), DeleteFocusedPage(), and DeletePageAtIndex() for related background.


Page 3 behavior configuration.

Page 3.

Page 3 demonstrates basic behavior configurations. To simplify the demo, settings may be applied to multiple modules.

  1. AuxTools_DisappearAtWidthLessThan

    AuxTools_DisappearAtWidthLessThan preserves FocusButton™ caption visibility against infringement from the AuxTools™ region. AuxTools™ are hidden when FocusButton width is reduced below AuxTools_DisappearAtWidthLessThan pixels. The demo applies this setting only to the main (top) FocusControl. Effects are observed by sliding the (un-beveled) right side splitter left and right. Mouse over the right side of the PM04 module to find the splitter.

  2. Auto-number Pages

    The PageNavCaptions_Number property of each FocusControl™ interface applies page numbering to the FocusButton™ caption and navigation buttons of the NavigationWindow™.

  3. EPM, Focus Caption Visible

    The FocusButton_Caption_Visible property of each FocusControl™ interface controls caption visibility, and, in left or right alignments, draws the FocusButton™ to alternate, preset FocusButton_Width_LeftOrRightAligned or FocusButton_Width_LRAlignedCaptionNotVisible widths.


    The FC_Align property of each embedded module's FocusControl™ interface controls individual FocusControl™ alignment, and can be set to FC_AlignTop, FC_AlignLeft, or FC_AlignRight. The demos apply the selected value to all of the embedded page modules. Spatial management is automated. Intended (original) page height is retained from configuration to configuration.

  5. EPM, Focus Controls Visible

    EPM, Focus Controls Visible toggles the Visible property of each FocusControl™ interface. The demos apply the value to all of the embedded page modules. Spatial management is automated.

  6. On Focus Page, Render To Page Height

    On Focus Page, Render To Page Height toggles the RenderToPageHeightOnFocusPage property of the RelTop, RelBot, and Status modules to true, causing these regions to automatically resize to preset heights (if any). Pages added by AuxTools are assigned a PageHeightOnFocusPage value of -1, and therefore will not resize (by intention, to illustrate exemption from the behavior). Pages generated by the initial mass propagation are assigned incrementally greater PageHeightOnFocusPage values. Higher numbered pages therefore resize to greater page heights.

  7. MINIMIZE V Sizable Pages w Sizing Handlers

    For the sake of code examples, shows how to resize regions by setting PageParent_Height.

  8. MAXIMIZE V Sizable Pages w Sizing Handlers

    For the sake of code examples, shows how to resize regions by setting PageParent_Height.

  9. Center Navigation Window in Desktop Workarea

    Center Navigation Window in Desktop Workarea sets the NavigationWindowPrescription CenterInDesktop property of all PM04 modules to true.

  10. Wrap_OffAtWidthLessThan

    Wrap_OffAtWidthLessThan protects the main paged region from undesirable infringement by forking to single row drawing when client region width is less than Wrap_OffAtWidthLessThan. Demos allow undesirably low settings. To observe effects, drag the right side splitter left and right.

  11. Paged Toolbars, Captions_Visible

    Paged Toolbars, Captions_Visible sets Page.Toolbar.Captions_Visible to true for all of the pages of the paged toolbar regions. As the scope of the Captions_Visible property is global to the Tools collection of the page, this causes the Margin_Captions_Visible property to be applied to the entire collection, and the wrapping method to abide by the ToolHeight_Captions_Visible and ToolWidth_Captions_Visible properties of the toolbar.

  12. ToolsTop OnWrap event handler test message

    ToolsTop OnWrap event handler test message illustrates when the ToolsTop.OnWrap event is fired, which is only when wrapping (re-draw) is actually performed.

  13. BorderConfiguration

    BorderConfiguration sets the root module BorderConfiguration property.

  14. Integral ConnectedToServer behavior

    To understand the demonstrated behavior, see Handling the Integrity of an Application's Connection to its Server.


Page 4.

ColorSchemes streamline the application of color across modules and page populations. Typical usage may simply accept the default Scheme, but full design flexibility is supported. See TADVANCE_ColorScheme for further information.


Page 5.

Page 5 processes demonstrate secure and general navigation. See How Page Security is Treated by Navigation Methods and the Navigation Window for background information. Observe effects in the FocusButton caption and NavigationWindow.


NavigationWindow behaviors are documented in the Automated Navigation Window Behavior topic. Scrolling state behavior can be tested by scrolling the focused page from view, closing, and re-opening the NavigationWindow. Areal utilization can be tested by dragging the main window to re-position FocusButtons within the desktop workarea before re-opening.


UPC™ SizingWindow.

From left to right, SizingWindow tools are minimize, normalize, or maximize width; minimize, normalize, or maximize height; minimize, normalize, or maximize height and width; and close.

TADVANCE_PMInterface.SizingEvents documents how the SizingWindow dynamically configures itself to existing sizing event handlers. Developers only have to write the handlers their implementation requires.


© Copyright 1995-2007, by ADVANCE Information Systems, Inc. ALL RIGHTS RESERVED.Copyright 1995-2007, by ADVANCE Information Systems, Inc. ALL RIGHTS RESERVED.

Firefox™.Best viewed in Mozilla Firefox™.