Ben, IIUC your proposal is very similar to what I wrote above, except
that I would have added the "virtual" aspect to TIME field itself. But
in the end, it seems we can have our cake and eat it too: we can
implement this with a channel filter and have the resulting flexibility,
while at the same time treating the ".TIME" part of the PV name as
special syntax that creates a channel filter (which is already the case
for "[n]" for arrays or "$" for long strings).
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1182091
Title:
Make TIME field directly accessible
Status in EPICS Base:
Triaged
Bug description:
Users often request the ability to access the TIME field directly.
It could be provided as an array of 2 32-bit values, possibly with a specific string in ISO-8601 form say.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1182091/+subscriptions
- Navigate by Date:
- Prev:
[Merge] ~bfrk/epics-base:scalar-get-optimization into epics-base:7.0 Ben Franksen via Core-talk
- Next:
[Bug 1182091] Re: Make TIME field directly accessible Ben Franksen via Core-talk
- Index:
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:
[Bug 1182091] Re: Make TIME field directly accessible Ben Franksen via Core-talk
- Next:
[Bug 1182091] Re: Make TIME field directly accessible Ben Franksen via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|