[NFBCS] JAWS Script Question

[Ty Littlefield]

Hi Doug,

Thanks again. Just wanted to drop a note that this worked perfectly. I 
used a combination of PriorLine/Next Line followed by the event you 
mentioned to speak the change and this works great.

Thanks again!


On 12/3/2024 2:41 PM, Doug Lee via NFBCS wrote:
> In a nutshell, wrapping event functions; but which event function(s) depends on your situation.
> FocusChangedEvent, CaretMovedEvent, and ActiveItemChangedEvent are examples.
>
> On Tue, Dec 03, 2024 at 02:17:38PM -0700, Ty Littlefield wrote:
> Hi doug,
>
> Thanks so much for your reply. I'm not super great with scripts; can you
> explain what you mean re: event processing?
>
> Thanks again,
>
> Ty
>
>
>
> On 12/3/2024 2:00 PM, Doug Lee via NFBCS wrote:
>> priorLine and nextLine functions request moves but may not necessarily wait to return until they are
>> accomplished. It is often sufficient to put a pause() call below those before speaking. In more obnoxious
>> circumstances, event processing is more effective. You may also find the SayLineUnit function in default.jss
>> an interesting alternative for wrapping, depending on your environment.
>>
>> On Tue, Dec 03, 2024 at 12:56:03PM -0700, NFBCS mailing list wrote:
>> Hi all,
>>
>> I'm trying to reproduce the edsharp indentation level announcements since I
>> often lose track of where I am in vs.
>>
>> I'm wrapping PriorLine and NextLine so that I can get the indentation level
>> before and after the move.
>>
>> I'm confused about how this is working; here's my debug script:
>>
>> SayString("debug "+GetLine())
>> PriorLine()
>> SayString("debug "+GetLine())
>> This speaks the line I was on twice, whereas the second SayString should be
>> speaking the line I'm currently on. I'm confused why/how this is happening,
>> and if there's a better way to go about this.
>>
>> For example, If my file reads:
>>
>> a
>>
>> b
>>
>> c
>>
>>
>> and I'm on b, if I navigate up from b I expect to hear:
>>
>> debug: b
>>
>> debug: a
>>
>> instead I hear:
>>
>> debug: b
>>
>> debug: b
>>
>> The same issue exists going down a line.
>>
>>
>>
>> Thanks,
>>
>>
>> Ty