In forms you can create buttons in the form of index cards. Index cards are usually applied to hold sub-lists or to form selectable form segments. Just like in an index card box, several index cards are stored on top of each other and form an index card system. one form can only contain one such index card system. The corresponding index cards are created in the selection master. They must all be assigned to a button area, i.e. either the NoSelect button area or the Select button area. There are no functional differences, however it is recommended to use the NoSelect button area.
For an index card you enter the macro @TAB P:TEXT in the Text field of the item master. Placeholders and meanings are listed here:
Placeholder | Meaning |
P |
Position of the index tab, where : T = Top (above card) B = Bottom (below card) L = Left (left at the card) R = Right (right at the card) |
Text | Text in the tab |
You can place any masks on index cards (lists and forms).
The functionality is realized with the help of the userexit iwf_cyc_lis as function call for each index card. The userexit puts an activated index card into the foreground and opens the mask which has been passed to the userexit as a parameter. The mask change organised in that way can be compared to opening autonomous masks on the desktop. The Pre_ and Post_Action triggers of the corresponding masks will work. When calling the combined form using iwf_frm_lis you should make sure that in the parameter string you pass the sub-mask which is to be visible on the first index card (alternatively @> is possible, too). It must correspond to the sub-mask you pass to the first index card as parameter for iwf_cyc_lis.
At changing index tabs / masks one sub-mask is closed and another one is opened. The corresponding Pre_- and Post_Mask triggers of the sub-masks will work. Additionally, a refresh is performed. At this moment the following Pre_- and Post_Action triggers will work:
For version 4.1- or higher DataView supports only index card systems with index tabs positioned in one line. The tab widths depend on their lables. If the width of the index card system is unsufficient, scrollbars are automatically added.
With the row- and column values of the first index card (fields Row and Column of the menu-item relation) you define the absolute position of the index card system in the header form. The line- and column values of all subsequent index cards are of no consequence.
With the length and width values of the first index card (fields Length and Width of the item master) you define the size of the index card system after opening the combined form. The length- and width values of all subsequent index cards are of no consequence.
With the length and width values of the sub-masks on the index cards (fields Length and Width of the mask master) you control the behaviour of the index card system in case of changes to the size of the header form (autoresize):
*If you select absolute dimensioning in both cases, you should match the length and width values of the sub-masks with the ones of the first index card.
As opposed to push buttons, index card systems in combined forms are always visible. If the header form or a sub-mask on the index card is in mask-edit state, you cannot browse the index cards.