![]() By default the MouseDown action is executed on KeyDown (press key) and the MouseUp action on KeyUp (release key). MouseDown, MouseUp), which is to be executed when a key event occurs (KeyDown, KeyUp). The mouse button was pressed prior to that outside of the element.Ī hotkey can be used to define a key or key combination and link it with a follow-on action (e.g. This mouse event occurs when the mouse button is released on the element. It is irrelevant whether the mouse button is pressed or released. This mouse event is triggered when the cursor is moved within the element. This mouse event is triggered when the cursor leaves the element. This mouse event is triggered when the cursor is dragged to the element. It is irrelevant where on the visualization the mouse button is released again. This mouse event is triggered when the mouse button is pressed while the cursor points to an element. This mouse event is triggered when the cursor points to an element and a full mouse click (pressing and releasing the mouse button) is executed on this item. It therefore has to be assigned to one of its elements. Currently there is no way to define such a property for the entire visualization. It therefore does not respond to each dialog closing action. Note: This property is not limited to the element, for which it is configured, but applies within the entire visualization. This event is triggered if one of the dialog boxes that were opened for user inputs is closed within a visualization. The following input events are available for an element: Each input action can be assigned any number of follow-on actions. Click on "Configure…" to open the Input Configuration, where you can assign follow-on actions. As long as no follow-on actions are defined, "Configure…" appears in the Properties field. Here you can define the consequential action that should be performed when the user makes an input in the element in online mode. The values in the project variable are used, if the variable defined in "Color change" is TRUE. They overwrite the values that are currently defined in "Colors". Variables of type DWORD for defining the frame and fill color for the element in alarm state. ![]() The values in the project variable are used, if the variable defined in "Color change" is FALSE. Variables of type DWORD for defining the frame and fill color for the element. Colors with definitions starting with “16#00” are invisible, since they are fully transparent.īoolean variable, which controls the switching of the element color between "normal state" (variable = FALSE) and "alarm state" (variable = TRUE). The transparency is indicated by the first two digits after “16#”. ![]() In TwinCAT 3, in addition to the RGB components, the color transparency can also be defined with the hexadecimal number. The structure of the hexadecimal number differs, compared to TwinCAT 2. The DWORD has the following structure: 16#TTRRGGBB In addition, the variables are used to specify the transparency of the color (FF: fully opaque - 00: fully transparent). A color is defined based on a hexadecimal number consisting of red, green and blue (RGB) components. The color variables used for dynamic definition of the element colors via project variables of type DWORD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |