2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 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: | Re: dataAccess V4 Ca client propertyId questions |
From: | Ralph Lange <[email protected]> |
To: | Kay-Uwe Kasemir <[email protected]> |
Cc: | EPICS Core Talk <[email protected]> |
Date: | Tue, 28 Jun 2005 15:38:39 +0200 |
Kay-Uwe Kasemir wrote:
Hi:How does it get started, i.e. how does it know how to find properties associated with the pvname?I forgot the circumstances, but one point at the SLAC meeting was that we might have to abandon the idea of "fred" == "fred.VAL". If you want the default value, you'll have to use "fred.value" in the new command-line 'caget' or the 'probe' GUI. If you use "fred", you will get _all_ properties of fred. It'll be consistent for the whole hierarchy: In case "fred.limits" is a structure, "fred.limits" will get all structure elements. "fred.limits.display.high" might drill down to a structure element.
Yes. But maybe not quite exactly.Have a look at the wiki page where Andrew describes the idea of Views. For me, that's a really really promising way to go. Grouping things in a reasonable way, providing flat as well as deep structures, use of parameters, there's a lot of good stuff in there. Gains attraction while you think about it.
http://www.aps.anl.gov/epics/wiki/index.php/V4_Standard_Properties_and_Events#Views
Ralph