Sounds good to me.
Please also make NAN, INF and friends a "no event at all".
Sure? It may conflict with shortcuts for New Acquisition Number" or
something similar.
At the moment, "NAN" would be a named event. If you post it and nobody
listens, nothing happens. But if there is a record on "NAN" Scanning,
you can trigger it.
I don't care which way to go, but the implications should be considered.
I have pushed my work so far (without NAN and INF handling) here:
https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+ref/named-events-backward-compatibility
I was about to start writing tests...
- References:
- Re: Scanning on event number fails with EPICS 3.16 Andrew Johnson
- Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- Re: Scanning on event number fails with EPICS 3.16 Ralph Lange
- Navigate by Date:
- Prev:
Re: Scanning on event number fails with EPICS 3.16 Ralph Lange
- Next:
Re: Scanning on event number fails with EPICS 3.16 Johnson, Andrew N.
- 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:
Re: Scanning on event number fails with EPICS 3.16 Ralph Lange
- Next:
Re: Scanning on event number fails with EPICS 3.16 Johnson, Andrew N.
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·