On Wed, 19 Dec 2001 13:41, [EMAIL PROTECTED] wrote:
> It is prevented from doing so by the following chunk of code in the log
> method of class Logger:
>
> if( m_logTargetsForceSet && m_additivity && null != m_parent )
> {
> m_parent.output( event );
> }
>
> m_logTargetsForceSet is only set when a target is added but as logger3
> uses the inherited handler and not one of its own, it only logs to
> LKAdd2.txt and refuses to log to any parent targets.
>
> I could not find any description as to how additivity is actually handled
> so is this a defect?
This is a defect. Im not sure exactly how to fix it though. If we didn't
check m_logTargetsForceSet then the class would print out twice to the
targets inherited from logger2. You got any ideas on how to fix this without
large overheads?
--
Cheers,
Pete
------------------------------------
The two secrets to success:
1- Don't tell anyone everything.
------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
