Security for graphic elements
There are two ways to secure graphic elements on a screen:
- Disable a property in the Appearance category.Clearing theEnabledproperty for a graphic element prevents touch and key events for the graphic element. The graphic element appears cross-hatched regardless of the access assigned to the screen. Use this method if, for example, to disable a graphic element during a particular machine state. It is typical to set this security through binding for use at runtime.
- Access property in the Security category.TheAccessproperty in theSecuritycategory works with theEnabledproperty and the cross-hatch functionality of graphic elements. WhenAccessis set to Inherit, the graphic element uses the security of the current screen to either show the graphic element as enabled or disabled and cross-hatched. For example, if the screen is Read Only,Accessis set to Inherit, andEnabledis selected, the graphic element appears cross-hatched. If the current screen security changes to Full Access, this enables the graphic element.WhenAccessis set to Full Access, the graphic element uses the state of theEnabledbox to determine if the graphic element it is enabled or disabled and displays cross- hatched regardless of the security of the current screen. Use Full Access to enable a button with a screen navigation command even if the screen is ready only. The user on the HMI device can then navigate the project in Read Only mode. This enables all commands for the button, not just the screen navigation.
Provide Feedback