On 11/04/2013 12:52 PM, Michael Davidsaver wrote:
I made a quick attempt to add posting of DBE_PROPERTY events to give
notification of CA meta-data changes. A new record field attribute is
added to identify meta-data fields. Monitors are posted from dbPut()
whenever a meta-data field is written, even if the value doesn't change.
Great -- I didn't realize there was so little left to do to finally
implement this, although I had been thinking about it for some time. I
just pushed a change to add the proc attribute value to the output
printed by dbDumpField() and dbWriteRecordType().
I also marked the alarm severity fields HHSV, HSV, LSV and LLSV as
prop(YES) for all DBF_DOUBLE-valued records, because changing them
to/from NO_ALARM changes the alarm limits reported in a DBR_GR_DOUBLE
to/from NaN. There may be a few other fields that we need to mark but I
can't think of any right now.
This will also need release notes, modifications to the AppDevGuide to
document the prop() attribute, and checking with vdct to see if it
accepts this attribute in a DBD file.
Advertising may be described as the science of arresting the human
intelligence long enough to get money from it. -- Stephen Leacock
- Re: posting DBE_PROPERTY Michael Davidsaver
- posting DBE_PROPERTY Michael Davidsaver
- Navigate by Date:
Re: db_create_event_log Andrew Johnson
[Merge] lp:~epics-core/epics-base/3.15_libcom_from_cvs_trunk into lp:epics-base Jeff Hill
- Navigate by Thread:
posting DBE_PROPERTY Michael Davidsaver
Re: posting DBE_PROPERTY Michael Davidsaver