Re: Some mouse navigation questions
toggle quoted messageShow quoted text
I think we should devote a separate thread for it, but to give you a short answer:
Those of you coming from JAWS scripting world might be familiar with the terms “script” and “function”. They are essentially the same: both perform something which can be called upon from other places. The crucial difference is how it is invoked: a script is a function with a piece of input attached.
In the same way, NVDA code can define functions (they are really Python functions). Just like JAWS scripts, the one difference between a function and a script is how you invoke it: you need a piece of input to invoke a script (basically a specially tagged function), which can call other functions, run other scripts, and even kill NVDA (if you want, but don’t try that at home). As long as any kind of command is assigned to a script (keyboard command, a touchscreen gesture, a braille display hardware button, etc.), NVDA will let you perform something. This is why you can assign touch commands to keyboard commands and vice versa, because NVDA do let you assign (technically called “binding”) all sorts of input mechanism for a command (for instance, just as you can use keyboard to perform object navigation routines, a set of touch swipes has been defined to perform object navigation; in fact, these commands call the same routine).
From: firstname.lastname@example.org <email@example.com> On Behalf Of Mary Otten
Sent: Friday, February 15, 2019 9:16 PM
Subject: Re: [nvda] Some mouse navigation questions
Good idea. There is probably some programming thing that gets in the way. I hope not though, because it makes very much sense.