Luke, From all of your suggestions the more I liked better was the "Keyboard and Gesture Management". "Edit Key Commands and Touch Gestures" isn't bad either, yet too verbose and

I have always thought calling it "input Gestures" was a bit absurd, seeming to prioritize the idea of touch gestures over keys in the language, when exactly the opposite is the case in practical

Why? There are not and never have been terminal/command line commands (other than for starting it) for NVDA. There is absolutely no legitimate context for that interpretation. We are talking about

Good idea, but no. I interpret that as" terminal commands" not keyboard and gesture commands." Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as

Why not "Manage commands" and "Commands help"? After all, keystrokes, from a keyboard or Braille display, touchs on screen and so on, are all commands for NVDA... Rui Fontes Às 19:57 de

Hi. That won't work by itself. You need to actually go into the properties of the .ini file as an administrator and change their ownership settings in the security tab. I was able to do this after a

I see. I thought NVDA key 1 was input gestures but evidently, it's just input help. Input help is a reasonable name for that feature. Manage commands sounds alright for the dialog. Gene -----

Run Notepad as an administrator. 1) type notepad.exe in the search window. (press windows key or go to start menu to get there). 2) Right-click (applications key, shift f10, NVDA's right

Why not something simple like “managing input“ or “manage input.“ That would cover all forms of input: keyboard voice, and so on.

Hi, We’re talking about two different things: the suggested text refers to what is now known as “Input Gestures” dialog. NVDA+number row 1 may change to something more descriptive and not too

Manage commands means that you can define or redefine or map commands by invoking the NVDA 1 command. Why not just call it what it is, keyboard and gestures help. Or something else, if there is as

Hi, I am trying to change the pause length in the .ini files for the oneCore voices. But it won’t let me save my new settings once I edit the ini files in notepad. I also tried copying, editing

Hi, I see. Quentin, any thoughts? I’m willing to work on this for 2019.3 provided that we get more user feedback. Cheers, Joseph

Joseph, It makes a lot more sense than what's there now. That being said, one of my points is that there are times when brevity serves an important purpose and others where it

Hi, Hmmm, I see. How about renaming it to something to the effect of, “Manage commands”? That may allow the original intent to be kept while making it more user friendly. It may also allow

Being a tech geek from way back, I can categorically state that this is yet another instance where "tech brevity" is being valued over end user understanding. It happens again and again and

That is an invalid assumption. Gestures means something you do to indicate something or something you do on a screen. When have the developers ever once, before the advent of the touch screen, heard

Hi, I like the oneCore voices, but is there any way to greatly decrease the amount of time they pause when they encounter punctuation marks? Eloquence has a much shorter pause than the oneCore

Hi, Other screen readers exhibit the same problem: JAWS calls it “keyboard help”, while Narrator calls it “input learning”. VoiceOver on iOS just calls it “help”, which is more

Hi, I think part of the reason for going that route is our (NVDA developers’) assumption that gestures can encompass input methods such as keyboards, touch, braille, and so many possibilities. JAWS