diff --git a/RELEASE_NOTES.html b/RELEASE_NOTES.html index ee605143e..fcef3c4ce 100644 --- a/RELEASE_NOTES.html +++ b/RELEASE_NOTES.html @@ -9,7 +9,9 @@
IOC resident CA server
Symptom: IOCs produce unexpected "ca put callback timeout" @@ -20,8 +22,49 @@
dbCommon.dbd
+UDF how has a promptgroup. This allows database configuration tools to mset UDF false.
+ +mbboRecord
+ +Field VAL now has a cvt_dbaddr method. +If any state strings are defined the field type and dbr_field_type are declared ENUM. If no state strings are defined then the type is USHORT. Previously the types were always ENUM.
+ +mbboRecord
+ +mbboRecord now implements method cvt_dbaddr for the VAL field. If no state vales or state strings are defined then it sets field_type and dbr_field_type to DBF_USHORT.
+ +camacDev
++ai and ao now support special_linconv. NOTE: NOT TESTED.
+ +drvGpib.c
+Add some cacheFlush statements
+ +aiRecord and aoRecord: Setting eoff=egul
+ +Instead of init_record executing code like
+ if ((pai->linr == menuConvertLINEAR) && pdset->special_linconv) {
+ pai->eoff = pai->egul;
+ }
+
+
+It now executes:
+ if ((pai->eslo==1.0) && (pai->eoff==0.0)) {
+ pai->eoff = pai->egul;
+ }
+
+aoRecord has a similar change
+ +This was done so that old device support which does not implement +special_linconv still works.
+ +CA puts to disabled record
+ +If a CA client issues a put to a disabled record then, when the record is +enabled, database puts to the record will not make the record process until +a CA put is again issued. This is fixed
dbb - database breakpoints
The database breakpoint facility was not working. This has probably been @@ -65,10 +108,13 @@ occur when recGblGetTimeStamp is called.
This now returns a non zero value if the result is nan (not a number).
+dbCa
+ +Improved diagnostic message.
+CA server (rsrv)
-Fixed race condition occuring when a put notify is canceled by a ca clear -channel at the same instant that it completes. This problem was introduced in +
Fixed race condition occuring when a put notify is canceled by a ca_clear_channel at the same instant that it completes. This problem was introduced in R3.13.5.