On 12/05/2013 01:45 PM, Mark Rivers wrote:
Nope, that won't work, because streamDevice does not currently use
the asynTrace facility to print error messages. I've suggested that
Dirk change StreamDevice to do this, but it is non-trivial because
most of StreamDevice is not aware of asyn, and does not necessarily
have access to the required asynUser structure when it needs it.
If StreamDevice used the errlogPrintf() API from libCom (errlog.h) then
you could at least use 'eltc 0' to disable the messages. I would only
want to do that temporarily because it turns off all errlog messages,
but it is useful when you can't see what you're typing because of the
volume of output.
- Andrew
--
Advertising may be described as the science of arresting the human
intelligence long enough to get money from it. -- Stephen Leacock
- References:
- StreamDevice "No reply from device" messages John Dobbins
- Re: StreamDevice "No reply from device" messages Eric Norum
- RE: StreamDevice "No reply from device" messages Mark Rivers
- Navigate by Date:
- Prev:
RE: StreamDevice "No reply from device" messages Mark Rivers
- Next:
Re: StreamDevice "No reply from device" messages Dirk Zimoch
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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: StreamDevice "No reply from device" messages Mark Rivers
- Next:
Re: StreamDevice "No reply from device" messages Dirk Zimoch
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|