Hi,
In 2015 there was some discussion on Tech-Talk about how to force a callback for a parameter that had not changed values.
Mark Rivers suggested a work-around, as shown below.
I wonder if anyone has an update on the situation since then? Has any other method appeared? Or did you have success with the work-around?
Thanks,
-Chris Ford, SLAC
On16 Nov 2015 Mark Rivers writes:
> If a driver wants to force a callback there is a method that does not require any changes to the base classes, e.g. exposing statusChanged_ as protected or adding a new
> isMotorRecordnowFilterButAlwaysProcess_ flag. The driver simply needs to set a parameter to a different value from present and then back to its current value, for example
> setDoubleParam(pC_->motorPosition_(position+1.);
> setDoubleParam(pC_->motorPosition_(position);
> callParamCallbacks();
- Replies:
- Re: asyn: what if a driver wants to force callbacks? Torsten Bögershausen
- References:
- Area Detector question Jörn Wüstenfeld
- RE: Area Detector question ulrik.pedersen
- RE: Area Detector question Mark Rivers
- Navigate by Date:
- Prev:
Re: asyn build on cygwin fails Ana Malagon
- Next:
RE: asyn build on cygwin fails freddie.akeroyd
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Area Detector question Mark Rivers
- Next:
Re: asyn: what if a driver wants to force callbacks? Torsten Bögershausen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|