You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In asynPortDriver.cpp most of the asynPortDriver::writeXXX() methods do this:
/* Set the parameter in the parameter library. */
status = (asynStatus) setXXXParam(addr, function, ...);
/* Do callbacks so higher layers see any changes */
status = (asynStatus) callParamCallbacks(addr, addr);
if (status)
whereas asynPortDriver::writeFloat64() does this:
/* Set the parameter and readback in the parameter library. */
status = setDoubleParam(addr, function, value);
/* Do callbacks so higher layers see any changes */
callParamCallbacks(addr, addr);
if (status)
I see problems in both versions: In the first case the status from the setXXXParam() call is being discarded; in the second the status from callParamCallbacks() is lost. Whatever the correct behavior should be I would expect all the types to implement the same error handling.
The text was updated successfully, but these errors were encountered:
In asynPortDriver.cpp most of the asynPortDriver::writeXXX() methods do this:
whereas asynPortDriver::writeFloat64() does this:
I see problems in both versions: In the first case the status from the setXXXParam() call is being discarded; in the second the status from callParamCallbacks() is lost. Whatever the correct behavior should be I would expect all the types to implement the same error handling.
The text was updated successfully, but these errors were encountered: