[jawsscripts] Re: logging multiple debug statements for later examination?

  • From: "Homme, James" <james.homme@xxxxxxxxxxxx>
  • To: "jawsscripts@xxxxxxxxxxxxx" <jawsscripts@xxxxxxxxxxxxx>
  • Date: Mon, 1 Feb 2010 15:46:14 -0500

Hi,
The only way I know this would work right would be to get every single possible 
event function and make it call some sort of debug script that would then right 
data to a file. You'd get an awful lot of information.

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 Mike O'Brien
Sent: Monday, February 01, 2010 12:40 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: logging multiple debug statements for later 
examination?

Hi Jeff

I prefer to use AppendToClipboard rather than SayString for debugging
messages.  I put a CopyToClipboard statement into the AutoStart function to
clear the clipboard, then use the AppendToClipboard to write any debugging
information I want.  Then when the script has run, I open or switch to
NotePad, or the favorite text editor, clear whatever it may contain, and
then paste  the clipboard.  Then I can study it all I want.  As the e-mails
about piping a string variable to a txt file pointed out, it's not that
simple to write to a file from a JAWS script.

-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman
Sent: Monday, February 01, 2010 2:24 AM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] logging multiple debug statements for later
examination?

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

__________
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

Other related posts: