Hi Mark, I've done JAWS scripting for a while one, and I always wondered how to make OutputDebugString work. Thanks for the very clear post. Jim Jim Homme, Usability Services, Phone: 412-544-1810 Internal recipients, Read my accessibility blog -----Original Message----- From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Mark A. DeMichele Sent: Tuesday, February 02, 2010 7:55 AM To: jawsscripts@xxxxxxxxxxxxx Subject: [jawsscripts] logging multiple debug statements for later examination? I'm not sure how to respond to these yet. I only get a digest so I copied the original question into this e-mail. I subscribed for Individual + Digest now so I guess it will be easier in the future. Anyway, I use OutputDebugString. Here are some of the functions I set up for myself. void function logMsg(string msg) OutputDebugString(msg) endFunction void function logCallStack(string msg) var string callstack let callstack = GetScriptCallStack() logMsg("CallStackBegin: " + msg + "\n" + callstack + "\nCallStackEnd") endFunction void function debugObject(object o, int cid, string msg) logMsg("DebugObject: " + msg) logMsg("--role: " + ToString(o.accRole(cid)) + " - " + getRoleText(o.accRole(cid))) logMsg("--name: " + ToString(o.accName(cid))) logMsg("--state: " + ToString(o.accState(cid))) endFunction Then if you download DebugView from http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx You can see all you messages. I'm surprise no else mentioned this. I'm new to Jawsscript so maybe it's not a common practice to do this. I do sometime have to use SayString since I need to know what's happening in relation to things that Jaws normally says, but in cases where I don't need that this works well. From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx> Subject: [jawsscripts] logging multiple debug statements for later examination? Date: Mon, 1 Feb 2010 18:23:38 +1100 Hi Scripters. as per subject line, If I've got a number of things going on in a script, and I've got a number of SayString debug statements along the way gleaning bits of information which will help me determine the accuracy of my logic flow, or whatever the funky term is for that, How might I most optimally log those to a file for later more careful and thoughtful examination, rather than having them just all spoken out in a big stream by jaws as the script proceeds, and which of course I forget by the end of it? <smile.> would I use some kind of iniwrite functionality or something? or do people think it would be optimal to use the append to clipboard functionality and just have all the debug statements shoved on there, for later pasting into a file? any info warmly appreciated. Geoff c. __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates. __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts