update doc; fix bug in scalarAlarmSupport

documentation/RELEASE_NOTES.md

@@ -4,7 +4,8 @@ This document summarizes the changes to the module between releases.
 
 ## Master (June 2019)
 
-support is a new feature
+1) support is a new feature.
+2) processRecord is new
 
 ## Release 4.4.2 (EPICS 7.0.2.2, Apr 2019)
 

documentation/TODO.md

@@ -1,16 +1,10 @@
 TODO
 ===========
 
-monitorPlugin
--------------
-
-A debate is on-going about what semantics should be.
-
-Must test record delete.
+unlisten and detach
 -------------------
 
-Must test removing a record from the PVDatabase while a pvAccess client
-is attached. Also why do both unlisten and detach exists?
+Why do both unlisten and detach exists?
 
 
 create more regression tests

documentation/pvDatabaseCPP.html

@@ -36,7 +36,8 @@
 
 <div class="head">
 <h1>pvDatabaseCPP</h1>
-<h2 class="nocount">Release ? - June 2019</h2>
+<h2 class="nocount">Release ? - TBD</h2>
+Latest update 2019.06.19.
 
 
 <h2 class="nocount">Abstract</h2>
@@ -181,7 +182,7 @@ This has the code for processRecord, removeRecord, and traceRecord.
 <h2>exampleCPP</h2>
 <p>Example code is available as part of this release.
 <a
-href="http://epics-pvdata.sourceforge.net/docbuild/exampleCPP/tip/documentation/exampleCPP.html">
+href="https://github.com/epics-base/exampleCPP">
 exampleCPP
 </a>
 </p>
@@ -245,6 +246,9 @@ other functionality.</p>
      Each record uses the control and scalarAlarm support provided by pvDatabaseCPP.
    </dd>
 </dl>
+<p>
+It also creates records that can be used by clients to show example of the plugin support.
+</p>
 
 <h2>iocshell commands</h2>
 <p>Shell commands are made available via the standard DBD include mechanism
@@ -267,7 +271,7 @@ pvDatabaseCPP
       </dd>
 </dl>
 <p>In addition any code that implements a PVRecord must implement an ioc command.
-Look at any of the examples in <b>exampleCPP</b> to see how to implement shell commands.</p>
+Look at the examples in <b>exampleCPP/support</b> to see how to implement shell commands.</p>
 
 </div>
 </body>

src/support/scalarAlarmSupport.cpp

@@ -36,7 +36,6 @@ epics::pvData::StructureConstPtr ScalarAlarmSupport::scalarAlarmField()
 {
     return FieldBuilder::begin()
             ->setId("scalarAlarm_t")
-            ->add("active", pvBoolean)
             ->add("lowAlarmLimit", pvDouble)
             ->add("lowWarningLimit", pvDouble)
             ->add("highWarningLimit", pvDouble)
@@ -75,7 +74,6 @@ bool ScalarAlarmSupport::init(
     }
     pvScalarAlarm = static_pointer_cast<PVStructure>(pvsup);
     if(pvScalarAlarm) {
-       pvActive = pvScalarAlarm->getSubField<PVBoolean>("active");
        pvLowAlarmLimit = pvScalarAlarm->getSubField<PVDouble>("lowAlarmLimit");
        pvLowWarningLimit = pvScalarAlarm->getSubField<PVDouble>("lowWarningLimit");
        pvHighWarningLimit = pvScalarAlarm->getSubField<PVDouble>("highWarningLimit");
@@ -83,7 +81,6 @@ bool ScalarAlarmSupport::init(
        pvHysteresis = pvScalarAlarm->getSubField<PVDouble>("hysteresis");
     }
     if(!pvScalarAlarm
-       || !pvActive
        || !pvLowAlarmLimit || !pvLowWarningLimit 
        || !pvLowWarningLimit || !pvHighAlarmLimit
        || !pvHysteresis)