areaDetector driver unlock/lock for doCallbacksGenericPointer()

["Pearson, Matthew via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Mark,

 

In the areaDetector driver documentation it states this, for passing NDArray objects to registered plugins:

 

Call doCallbacksGenericPointer() so that registered clients can get the values of the new arrays. Drivers must release their mutex by calling this->unlock() before they call doCallbacksGenericPointer(), or a deadlock can occur if the plugin makes a call to one of the driver functions.

 

It seems to make sense, but wouldn’t that be an odd design to have a plugin call a driver function?

 

Most drivers seem to hold the mutex while calling doCallbacksGenericPointer (at least all the ones I just checked).

 

Cheers,

Matt