Smart Object Event
The primary purpose of a Smart Object event is to create a Smart Object that a user can double-click in a CimEdit screen and display a simple Smart Object Configuration dialog box instead of the detailed Properties dialog box. The user enters one or more values, as determined by the Smart Object event configuration. The Smart Object is ready for runtime use with no more configuration required.
Note: When the object is assigned a Smart Object event, a screen designer can select the object on the CimEdit screen and click Trigger Smart Object in the Home>Properties group on the CimEdit Ribbon bar to open the Smart Object Configuration dialog box.
You can protect your proprietary Smart Objects by preventing the interior logic from being examined. You do this by saving your CimEdit Screen as a runtime-only screen.
Field | Description | ||
---|---|---|---|
A | Action | Contains a drop-down list of existing procedures and scripts. Use either of the following. | |
Procedure | |||
Script | |||
B | Parameter | These entry points have no parameters. | |
C | Debounce event | Check | |
Clear | |||
Note: When debouncing is enabled, the event/action queue is always processed one action at a time; the current action must be completed before the next action can start. This makes the queue's event/action sequencing predictable and avoids situations where many events could trigger actions and consume unacceptable levels of CPU and memory. |
To protect your named Smart Object from being decomposed, you can save the CimEdit screen as a runtime-only screen (.cimrt ). As a result, another designer will be able to link the protected Smart Object, but not copy it or view the code.
- Same Smart Object Configuration dialog box that the CimEdit screen designer uses or,
- A dialog box that bypasses the CimEdit screen designer.
If you want to prohibit the CimView operator from opening the dialog box, you need to disable it through scripting.