Re: [twsocket] Logging class for TWSocket

2005-12-26 Thread Arno Garrels
Francois PIETTE wrote: A TIcsLogger could be linked to the ICS components Arno, I don't know how you intend to implement your logging classe but your last messages about compiler trouble make me thinking you are planning to change TWSocket base class to add logging feature. I don't

Re: [twsocket] Logging class for TWSocket

2005-12-26 Thread Francois PIETTE
, December 26, 2005 12:08 PM Subject: Re: [twsocket] Logging class for TWSocket Forgot to say that a base class eases conditional compile like: {$IFDEF NO_DEBUG_LOG} TIcsComponent = TComponent; {$ELSE} TIcsComponent = TIcsBaseLogComp; {$ENDIF} TCustomWSocket = class(TIcsComponent

Re: [twsocket] Logging class for TWSocket

2005-12-26 Thread Francois PIETTE
The loDestxx options specify a destination, either to event, file or to OutputDebugString. Would be interesting to have output to system log and application log. Do you mean Windows eventlog? Indeed. -- [EMAIL PROTECTED] http://www.overbyte.be -- To unsubscribe or change your settings

Re: [twsocket] Logging class for TWSocket

2005-12-26 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: Would be interesting to have output to system log and application log. Do you mean Windows eventlog? Indeed. I would avoid putting debug events in the existing logs, many applications interrogate them for unusual errors and they are often