re your first question about number at end of scheduleFunction, yes indeed! that's right. I can't see how this would really work decently for your situation either. isn't there some function one can call to determine whether synth is actually speaking or not? I've just looked through the Is" functions though and I can't see it now. ----- Original Message ----- From: "Dean Masters" <dwmasters@xxxxxxxxxxxxx> To: <jawsscripts@xxxxxxxxxxxxx> Sent: Tuesday, March 03, 2009 6:52 AM Subject: [jawsscripts] Re: ScheduleFunction > so the number at the end tells the scheduled function how long to wait > before it is run? the lines are different lengths and then you have others > who might use the scripts who have JAWS set at different speeds so I don't > guess this idea works. If the number was set too long then the lines would > be disjunct since I was thinking of recreating a SayAll so that the NextLine > doesn't go off and run away while JAWS is still trying to say the lines. It > catches up but skips a page or two while doing so. > > Dean > > ----- Original Message ----- > From: "Martin Slack" <m.g.slack@xxxxxxxxxxxx> > To: <jawsscripts@xxxxxxxxxxxxx> > Sent: Sunday, March 01, 2009 3:56 AM > Subject: [jawsscripts] Re: ScheduleFunction > > > | That depends on how long the line is which is to be spoken. What Jaws > does > | is to launch the Sayline function, then immediately launch the scheduling > | part of ScheduleFunction. You have asked in your code for three-tenths > of > | a second to pass before the NextLine function is called, so if Sayline > takes > | longer than that to speak, NextLine will be called before the speaking is > | fully over. If that happens, and if you can tell it has, you could always > | increase the value of the second parameter of ScheduleFunction, to give > more > | delay. > | > | hth > | > | Martin > | > | > | ----- Original Message ----- > | From: "Dean Masters" <dwmasters@xxxxxxxxxxxxx> > | To: "JAWS Scripts" <jawsscripts@xxxxxxxxxxxxx> > | Sent: Sunday, March 01, 2009 4:29 AM > | Subject: [jawsscripts] Re: ScheduleFunction > | > | > | > So if I wrote something like > | > > | > SayLine () > | > ScheduleFunction (NextLine (), 3) > | > > | > would the whole line be spoken before the NextLine be done? > | > > | > Dean > | > ----- Original Message ----- > | > From: "Cohn, Jonathan C [IT]" <Jonathan.C.Cohn@xxxxxxxxxx> > | > To: <jawsscripts@xxxxxxxxxxxxx> > | > Sent: Wednesday, February 25, 2009 10:35 PM > | > Subject: [jawsscripts] Re: ScheduleFunction > | > > | > > | > | The schedule function has the advantages: > | > | 1. It allows jaws to go off and do something else while waiting. > | > | 2. It can be disabled i.e. there is a unscheduled function. > | > | > | > | The disadvantage is that you need a separate script, and you need to > | > consider what happens if focus changes. So for example watching for a > | > focus > | > change away from your active window and then calling the unscheduled. > | > | > | > | The Communicator and Messenger scripts use the schedule function to > | > check > | > the status line for "is typing a message" or "is writing a message" and > | > then > | > produce ticking sounds and let you know that the other party is active. > | > | > | > | Best, > | > | > | > | Jon > | > | > | > > | > > | > __________ > | > 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 > | > > > __________ > 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