Posts: 40,483
Threads: 491
Joined: Aug 2002
See the documentation on that field value equals filter. It's not what you want to use, at least not by itself. You'd want to have first a 'is field change for'. Otherwise, every time any trigger shows up, and the field value is equal to True, it's going to run, no matter what type of trigger.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
06-02-2017, 08:27 PM
(This post was last modified: 06-02-2017, 08:28 PM by Dean Roddey.)
You could also avoid the extra field read, by replacing the FldValueEquals with:
Event Fld Equals(/cqsl.fldval/val, True)
When a field trigger occurs, the actual value that triggered is sent along with the event data. If you look at the format of the triggers:
http://www.charmedquark.com/Web2/CQCDocs...TriggerFmt
The 'path' for the field value in a field change event would be "/cqsl.fldval/val", so you can just get it from there, instead of going back to the driver and reading the field again (which may have even changed before you get a chance to look at it, so using the value that comes with the event is safer all around.)
So you'd first check is a field change for the field you care about, then do the above to check the field value that caused the trigger.
Dean Roddey
Explorans limites defectum