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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | asynPortDriver callParamCallbacks(); not working but callParamCallbacks(0); working |
From: | Hugot Sebastien via Tech-talk <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Mon, 18 Feb 2019 16:18:35 +0000 |
Hello, I was relieved to find the solution of an asyn problem I had (behavior change from 4-26 to 4-27). (https://epics.anl.gov/tech-talk/2015/msg01713.php) Now, when I use the code, setParamStatus(param, ASYN_SUCCESS); /* If it might previously have been
an error code */ setXXXParam(param, value); callParamCallbacks(); setParamStatus(param, ASYN_ERROR); /* Or other error */ callParamCallbacks(); does not update the value of my parameter, but with this version (using callParamCallbacks(0); instead of callParamCallbacks();) setParamStatus(param, ASYN_SUCCESS); /* If it might previously have been
an error code */ setXXXParam(param, value); callParamCallbacks(0); setParamStatus(param, ASYN_ERROR); /* Or other error */ callParamCallbacks(0); the parameter value is updated. Do you have any idea for such a behavior ? I am using asyn4-32. Sébastien.
Préservons notre environnement, n’imprimez ce mail que si nécessaire. Preserve our environment, print this email only if necessary. |