Fixed a bug when the using asynchronous device support, for example devBusyAsyn with an asyn port driver with ASYN_CANBLOCK. The problem occurred when 0 was written to the record, followed immediately by writing 1. If the record was still processing with the 0 value when the 1 was written, device support would not process a second time with the 1 value. It should have processed a second time with the 1 value (via the EPICS .RPRO field), but this was not happening.
configure/CONFIG no longer defines STATIC_BUILD=YES on any platform.
Added caQtDM display
Added autosave-request file busyRecord_settings.req.
Added .opi display file for CSS-BOY
Added busyRecord.db database, xxBusyRecord.adl medm-display file.
busyRecord.c rewritten to minimize differences from 3.14.11 bo record.
The busy record was reimplemented to permit device support to reset the VAL field to zero.This version is intended to build with EPICS base 3.14.10.
This is the first release of the synApps busy module.This version is intended to build with EPICS base 3.14.10. Suggestions and Comments to: