Yup, as Jeremy has indicated, only one "debugger" can be attached to that output at any one time. Does that mean it's working for you now? C.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy Coulter Sent: Friday, 22 May 2009 10:48 a.m. To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Capturing outputDebugString API yes I am. jeremy On Fri, May 22, 2009 at 10:45 AM, Jeremy North <[email protected]> wrote: Were you running your app under the debugger? On Fri, May 22, 2009 at 8:41 AM, Jeremy Coulter <[email protected]> wrote: > I did try that, but it didint seem to work which I found strange. > Maybe I did it wrong. I just ran it then ran my app. > > Jeremy > > On Fri, May 22, 2009 at 10:37 AM, Conor Boyd <[email protected]> > wrote: >> >> DebugView from SysInternals. >> >> No wheel-reinventing required. >> ________________________________ >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Jeremy Coulter >> Sent: Friday, 22 May 2009 9:58 a.m. >> To: NZ Borland Developers Group - Delphi List >> Subject: [DUG] Capturing outputDebugString API >> >> Hi all. >> >> Is there a way to capture "outputDebugString" other than using the >> EventLog? >> The EventLog is fine, UNTIL, you want to copy an output, so I thought I >> might write my own little capture tool. >> >> Anyone done/seen anything like this? >> I assume since its an API call I just need to listen to a message? >> >> >> Thanks, Jeremy
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
