Information

  • Below, you will find an overview of the settings to be made on the respective data items, so that different actions can be carried out on the corresponding data fields in user modules:
    • Links
    • Buttons
    • Context menu entry
    • Overwriting menu items
    • OLE with actions
ParametersLinkClick on the

individual context menu entry

Overwrite Menu ItemsAction on OLE
DFData item which is to be defined as a linkA context menu entry is embedded in the required data area as a data field DI004336 Button/IronPython.


A context menu entry is embedded in the required data area as a data field DI004336 Button/IronPython.


The action is carried out on data field DI004336 Button/IronPython, which is created in a separate data area in the required module.Data items of DI class "13" (OLE DIs) or DI 025581 (background)
DF behaviorDefines which object type is to be addressed via the button:
  • e2: Menu item
  • e4: Module/Macro
  • e5: Module subclass
Defines which object type is to be addressed via the button:
  • c2: Menu item
  • c4: Module/Macro
  • c5: Module subclass
Defines which object type is to be activated via the context menu command:
  • m4: Module call/Macro call
  • m5: Module subclass
Defines with which object type the menu item is to be overwritten:
  • d2: Menu item
  • d4: Module/Macro
Defines which object type is to be activated via Action on OLE:
  • a2: Menu item
  • a4: Module/Macro
  • a5: Module subclass
Action IDDefines which object is to be addressed via the link:

Depending on the DF behavior:

  • Module ID
  • Menu item ID
  • Macro ID
  • Method name from the module subclass

Here you can either enter the unique number of a particular object or a variable for the object in question.

Defines which object is to be addressed via the button:

Depending on the DF behavior:

  • Module ID
  • Menu item ID
  • Macro ID
  • Method name from the module subclass


Defines which object type is to be addressed via the context menu command:

Depending on the DF behavior:

  • Module ID
  • Macro ID
  • Method name from the module subclass
Defines with which object type the menu item is to be overwritten:

Depending on the DF behavior:

  • Module ID
  • Menu item ID
  • Macro ID
Defines which object is to be addressed via the action on OLE:

Depending on the DF behavior:

  • Menu item ID
  • Module ID/Macro ID
  • Method name from the module subclass
TooltipHere the text is entered which is displayed in the tooltip when moving the mouse over the link.

The entry can be a text and (or) variables.

Here the text is entered which is displayed in the tooltip when moving the mouse over the link.

The entry can be a text and (or) variables.




DF height

DF width


Height and width of the button


Symbol ID
Symbol number

Defines the button properties: color, font


Symbol 001807 is used in the standard system.
Symbol number

Defines the button properties: color, font


Symbol 001304 is used in the standard system.

If no symbol is assigned to a button, the symbol assigned to DI004336 in data item DI004336 Button/IronPython in DT400 will be used.




DF heading
Name of the button

If no DF heading is specified, the name of the corresponding object will be displayed.

Name of the context menu entry.

If no DF heading is specified, the name of the corresponding object will be displayed.



@L variable


Here you can enter the menu item to be overwritten.
Default values
Here you can store an OLE which will be displayed on the button. For this purpose, enter the DBOLE prefix and the number of the OLE object in brackets.
DBOLE(001007).
Here you can store an OLE which is displayed in front of the entry in the context menu. For this purpose, enter the DBOLE prefix and the number of the OLE object in brackets.
DBOLE(001007).

ParticularitiesThis function must only be used on output fields.Buttons can be summarized in button areas.Data field DI004336 Button/IronPython has to be customized in a visible window (windows 1-3).It is recommended to customize the DI004336 Button/IronPython data field in a separate data area and in window 9.

Notes

  • In all three actions,
    • the update mechanism of the @Ds is triggered.
    • the invoker_record is filled.
  • To open a method with data field behavior *5, it must have the following signature:
def my_method(self, applied_dfc, clicked_df):
    pass
PY