[jawsscripts] Re: logging multiple debug statements for later examination?
- From: Soronel Haetir <soronel.haetir@xxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx
- Date: Mon, 1 Feb 2010 08:29:29 -0900
I would go with building a string and then either write to a file
using something like the append to file script that got posted a few
days ago or dump it to the virtual buffer. The latter would most
likely be preferable since it doesn't leave clutter on disk.
On 1/31/10, Geoff Chapman <gch@xxxxxxxxxxxxxxxx> wrote:
> 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
>
>
--
Soronel Haetir
soronel.haetir@xxxxxxxxx
__________
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:
