Skip to content

Class: dbTabDialogView

Properties | Events | Methods | Index of Classes

Contains and provides coordinated access to dbTabView objects

Hierarchy

cObject > cUIObject > DfBaseObject > DfBaseWindow > DfBaseUIWindow > DfBaseControl > DfBaseList > DfBaseForm > DfBaseTabDialog > TabDialog_ > TabDialog > dbTabDialog_ > dbTabDialog > dbTabDialogView

Show full hierarchy and direct subclasses

Library: Windows Application Class Library

Package: Dftabdlg.pkg

Description

dbTabDialogView is used to contain and provide coordinated access to dbTabView objects. Each tab view displays a tab with its name on it within this object at all times. Each dbTabView object supports a separate DataDictionary object (DDO) structure.

The dbTabDialog class is a class similar to the dbTabDialogView class, which is used to contain and provide coordinated access to dbTabPage objects. The dbTabDialog class supports only one DDO structure for the entire dialog.

Sample

Object TabDialogView1 is a dbTabDialogView
    Set Size to 117 271
    Set Location to 10 15

    Object TabView1 is a dbTabView
        Set Label to "TabView1"
        :
    End_Object

    Object TabView2 is a dbTabView
        Set Label to "TabView2"
        :
    End_Object

End_Object

Syntax

Dftabdlg.pkg

Object oObjectName is a dbTabDialogView
    Set Size to height width
    Set Location to row column
    Set Rotate_Mode to RotateMode

    Object oObjectName is a dbTabView
        :
    End_Object

    Object oObjectName is a dbTabView
        :
    End_Object

End_Object

Of Special Note

The only visual objects that can be placed directly inside an object of this class are dbTabView objects. All other visual objects will be placed inside the dbTabView objects. Objects of this class must be placed inside another DEO container, usually a dbView.

DbTabViews are used when each tab page will contain a stand-alone view with its own DDO structure. In this case, a unique DDO structure will reside inside each dbTabView object. You may not use dbTabPage objects in objects of this class (place these in a dbTabDialog).

If there is not enough room in this object to fit all of the tab views, this object will scroll the tabs horizontally, or will create multiple rows of tabs by "wrapping" them.

Shadowing

Setting the enabled_state property to false will disable entry into all tab views inside this object. Individual tab views can be disabled by setting the tab view's button_shadow_state to true (the tab cannot be selected and the tab view cannot be displayed) or by setting the tab view's enabled_state to false (the button is enabled, the view can be displayed, but it cannot be entered).

The rotate_mode property allows you specify where next navigation should proceed from the last object of a tab view. Modes are supported to allow users to leave this object (RM_None), ring within the tab view (RM_Ring), ring within this object (RM_Rotate_in_Ring), and to rotate through all tab views once, exiting when the last object of the last view is departed (RM_Rotate).

DEO Container Object

This object is a data-entry container object (DEO container). A DEO container is an object whose native capabilities (in this case, those of a TabDialog) are augmented by data-aware behaviors. These behaviors include: The finding, clearing, saving, and deleting of records (and sets of records)Change verification (save, delete, and data-loss verifications) These data-aware "skills" are added to all DEO classes through a series of mixin classes. The messages are listed here, but documented in the mixin classes. You are encouraged to study the mixin classes. Information provided in these classes may be applied to all DEO classes (all db... classes). Those classes are: Nesting_Mixin, Navigate_Mixin, Verify_Mixin, Server_Mixin, and DEO_Delegate_Mixin.