SA Faceplate - Use of Pulse Function

Hi Rune, I totally agree with Stuart. One of the interesting things with the faceplate command buttons is the pattern we use to notify the operator whether the command has succeeded. With a func like Pulse, that just isn't possible.


To answer your question though, no you cannot use the Pulse function with super genie associations. But you can use its underlying function "Pulser" (Include/tag.ci). The reason for this is that the Pulse label does a "arg = arg" and the compiler doesn't support association resolution in that situation.

So:

1. Add a button_base genie from the sa_controls_common library on your faceplate and configure the "Click Command" to:
Pulser(?__EquipmentName?.YourDigital, "", VarToArrayIndex(?__EquipmentName?.YourDigital))
2. Add a button_label_12 genie over the button and give it an appropriate label. Link the label's background AN genie parameter to the AN of the rectangle object in the button named "Background".

This will compile and "work" at runtime. But... what Stuart said!

cheers,

bradley

Hi Rune, I totally agree with Stuart. One of the interesting things with the faceplate command buttons is the pattern we use to notify the operator whether the command has succeeded. With a func like Pulse, that just isn't possible.


To answer your question though, no you cannot use the Pulse function with super genie associations. But you can use its underlying function "Pulser" (Include/tag.ci). The reason for this is that the Pulse label does a "arg = arg" and the compiler doesn't support association resolution in that situation.

So:

1. Add a button_base genie from the sa_controls_common library on your faceplate and configure the "Click Command" to:
Pulser(?__EquipmentName?.YourDigital, "", VarToArrayIndex(?__EquipmentName?.YourDigital))
2. Add a button_label_12 genie over the button and give it an appropriate label. Link the label's background AN genie parameter to the AN of the rectangle object in the button named "Background".

This will compile and "work" at runtime. But... what Stuart said!

cheers,

bradley