| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: OPI updates when enum strings/values change |
| From: | Michael Davidsaver via Core-talk <core-talk at aps.anl.gov> |
| To: | Mark Rivers <rivers at cars.uchicago.edu>, Andrew Johnson <anj at anl.gov> |
| Cc: | "core-talk at aps.anl.gov" <core-talk at aps.anl.gov>, Kevin Peterson <kmpeters at anl.gov>, Matthew Newville <newville at cars.uchicago.edu> |
| Date: | Thu, 4 May 2023 08:37:28 -0700 |
On 5/4/23 08:30, Michael Davidsaver wrote:
On 5/4/23 08:23, Mark Rivers wrote:Hi Andrew, I looked to see how PREC and other fields support DBE_PROPERTY in EPICS base. I see that the ao, ai, etc. record dbd files put the attribute "prop(YES)" on fields that should generate DBE_PROPERTY callbacks. I just added prop(YES) to the PREC field in motorRecord.dbd and now when PREC changes Phoebus updates the window to the new precision instantly, without needing to close and re-open the window. This is great! A couple of questions: - If we were to add prop(YES) to fields in the motor record then it would require a minimum of base 3.14.11?It would actually be >= 3.15.0.2 https://github.com/epics-base/epics-base/commit/3cccdd813458936b536f51589a100cfcfd91f637
My mistake. This commit adds "prop(YES)" to the base .dbd files. The C .dbd file parser has always ignored unknown recordtype "items". (cf. dbRecordtypeFieldItem() ) so I think any 3.14 would ignore "prop(YES)".