On 3/20/20 6:32 PM, Mark Rivers wrote:
>> It's also not clear to me why you need a timeout on the dequeue step
>> at all. Are you using this to detect a device error?
> No, I am not using it to detect a device error. I am using because, for example, in continuous acquisition mode the dequeue routine is being called in an infinite loop. But when the user tells acquisition to stop that final frame will never arrive, so the dequeue function needs to time out and exit.
>
Rather than a timeout, I would use a special message to signal
the receiver to (maybe) break from its loop. In this case, a NULL
should do nicely.
- Replies:
- RE: C++ question Mark Rivers via Core-talk
- References:
- C++ question Mark Rivers via Core-talk
- RE: C++ question Mark Rivers via Core-talk
- RE: C++ question Mark Rivers via Core-talk
- Re: C++ question Michael Davidsaver via Core-talk
- Re: C++ question Mark Rivers via Core-talk
- Navigate by Date:
- Prev:
Build completed: EPICS Base base-3.15-562 AppVeyor via Core-talk
- Next:
RE: C++ question Mark Rivers 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:
RE: C++ question Mark Rivers via Core-talk
- Next:
RE: C++ question Mark Rivers 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
|