| 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: Scanning on event number fails with EPICS 3.16 |
| From: | Dirk Zimoch <[email protected]> |
| To: | <[email protected]> |
| Date: | Fri, 9 Feb 2018 14:52:15 +0100 |
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...