Restart NVDA with a single gesture

[LeonarddeR]

By default, ctrl+nvda+f4 is assigned, but we can consider removing this as well as change it to the current gesture for reloading plugins (ctrl+NVDA+f3).
Even though it is possible to restart NVDA using its desktop shortcut, this way of restarting appears to be much quicker and is a nice alternative for reloading plugins, which would allow for deprecating this as @jcsteh suggested in #6389. Furthermore, it works with portable copies.

The only thing I'm not sure about, do we just want to call core.restart, or use queueHandler.queueFunction(queueHandler.eventQueue,core.restart) as in gui.ExitDialog? I'm sure it's used there for a reason.

[jcsteh]

1. It's worth noting that despite my original reservations, I managed to
   fixed reload plugins in The reload plugins command no longer causes problems for triggered configuration profiles, new documents in web browsers and screen review. #6390 (pending review). So, the use case for
   this is somewhat less compelling now. Do you still think this is necessary?
2. Given that the use case is limited and that there are other ways of
   restarting NVDA relatively quickly (even NVDA+q, r, enter is pretty
   quick), I think this should be unbound by default. We're getting
   somewhat careful about using keystrokes for rarely used commands. :)

[derekriemer]

We could unbind reload plugins, and bind this to that.

On 9/21/2016 4:52 PM, James Teh wrote:

1. It's worth noting that despite my original reservations, I managed to
   fixed reload plugins in The reload plugins command no longer causes problems for triggered configuration profiles, new documents in web browsers and screen review. #6390 (pending review). So, the use case for
   this is somewhat less compelling now. Do you still think this is
   necessary?
2. Given that the use case is limited and that there are other ways of
   restarting NVDA relatively quickly (even NVDA+q, r, enter is pretty
   quick), I think this should be unbound by default. We're getting
   somewhat careful about using keystrokes for rarely used commands. :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#6396 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFGiva_N-tF3FAKYUM59Jj9gbKAcRgjnks5qsbUVgaJpZM4KDMmy.

---

Derek Riemer

• Department of computer science, third year undergraduate student.
• Proud user of the NVDA screen reader.
• Open source enthusiast.
• Member of Bridge Cu
• Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

[LeonarddeR]

if #6390 gets into master, I think an unbound gesture would be ok.
How about to decide whether to use queueHandler or not?

[jcsteh]

You should be okay to just call core.restart, since this is being done in a script where you're already in the core queue anyway.

[LeonarddeR]

I actually removed the gesture binding to ctrl+nvda+f4, so it is unbound now.

[feerrenrut]

Thanks, looks good. Are you able to comment on the testing that has been done on this? Has this been tested with dialogs open, or with addons installed? I think that the about dialog causes problems when trying to exit nvda, that might be to do with wx. It would be nice to know if this also had that behaviour.

[LeonarddeR]

I tested this both with the general settings and about dialogs open and I do not observe strange behavior.