Launching a new copy of NVDA should exit running version and start launched version.

[Qchristensen]

(Updated with command line information from Leonard).

This is a minor inconsistency, but still worth recording:

With any version of NVDA running, pressing control+alt+n restarts the installed copy of NVDA. That works fine.

If a desktop or start menu shortcut to NVDA is instead activated, or a copy of NVDA run from File Explorer, NVDA does not restart. NVDA does have a command line parameter -r to replace or quit the running version of NVDA and start this one (Thanks Leonard for reminding me of that!)

See https://www.nvaccess.org/files/nvda/documentation/userGuide.html#CommandLineOptions for more information on the command line options.

I would like to then propose that we make the -r parameter implicit and adopt that behaviour by default, and perhaps in its place add a parameter to check and return a value if there is already a copy of NVDA running to enable both functionalities going forward.

[Brian1Gaff]

Hmm, in many ways what you are describing is what I get when I've just updated nvda and it tries to auto restart. I have no idea what is going on behind the scenes for this, but generally, I tend to relaunch with the alt/ctrl n which does close the old copy. Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Quentin Christensen" <notifications@github.com> To: "nvaccess/nvda" <nvda@noreply.github.com> Cc: "Subscribed" <subscribed@noreply.github.com> Sent: Tuesday, May 22, 2018 2:15 AM Subject: [nvaccess/nvda] Launching a new copy of NVDA should exit running version and start launched version. (#8320)

…

This is a minor inconsistency, but still worth recording: With any version of NVDA running, pressing control+alt+n restarts the installed copy of NVDA. That works fine. If a desktop or start menu shortcut to NVDA is instead activated, or a copy of NVDA run from File Explorer, NVDA does not restart. For instance, I have the latest Next snapshot installed, but I have a desktop shortcut to a portable version of NVDA 2018.1.1. In order to launch that shortcut, I need to navigate to it on the desktop, press NVDA+q then enter to quit the running version of NVDA, then ENTER to launch the shortcut which has focus. Ideally, I should be able to have a version of NVDA running, navigate to my desktop shortcut, press ENTER to activate it and then my running copy of NVDA would automatically quit as the version the desktop shortcut points to starts. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #8320

[LeonarddeR]

The reason why NVDA restarts with the control+alt+n shortcut, is because the "-r" parameter is provided to the executable. This parameter closes a running copy of NVDA and then starts a new one. Adding the -r command line parameter should solve your issue.

Having said that, I agree that it could be considered to have this restarting behaviour by default.

[Brian1Gaff]

That is why when I want to automate getting the log from the previously running version I use a batch file and avoid running the shortcut as this would confuse things. Brian

[derekriemer]

having a restart implicit could be very nice indeed.

[michaelDCurran]

I can support this if that is what most people would prefer. The original idea however was that the user had to be quite specific about launching any random copy of NVDA and replacing the old one, just in case they accidentally executed the file.

[JulienCochuyt]

For a non-initiated user, I think it is less common to accidentally run an executable that it is to stumble upon trying to replace the current running NVDA with a portable version already created.

I already had a few hard times trying to remote assist grand beginners in accomplishing this task.

[XLTechie]

For what it's worth, either for myself or while supporting others, I have never run into a situation where someone accidentally had an executable copy of NVDA laying around, and ran it by mistake. This seems extraordinarily unlikely to happen for the novice users that -r was meant to help. Conversely, having to use -r when running NVDA, as has already been stated, makes the replacement of NVDA by those of us doing remote technical support, a more annoying and time consuming process. So, even though nobody asked, I whole-heartedly cast my vote behind this change.

[XLTechie]

So, is this still being considered? In other words: bump.:)

[josephsl]

Hi, based on comments, I’m thinking yes, but we’re blocked by Project Threshold at the moment; I myself am rebasing Project Threshold to various pull requests in the meantime and I’m sure NV Access will advise folks to do the same if a PR is going to be written for this one. Thanks. From: Luke Davis <notifications@github.com> Sent: Tuesday, July 16, 2019 6:33 AM To: nvaccess/nvda <nvda@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [nvaccess/nvda] Launching a new copy of NVDA should exit running version and start launched version. (#8320) So, is this still being considered? In other words: bump.:) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8320?email_source=notifications&email_token=AB4AXEESAIM4PC5LCSOVWFTP7XEYXA5CNFSM4FA7KHC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2A3OBA#issuecomment-511817476> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4AXEHTKJI2MM3DMH7YOQTP7XEYXANCNFSM4FA7KHCQ> .

[XLTechie]

@JulienCochuyt has already written a PR for this--a month or so ago, and an update yesterday.

[josephsl]

Hi, just saw that he has rebased it on master. I’ll perform Python 3 compatibility test, although I think edits are not necessary. Thanks. From: Luke Davis <notifications@github.com> Sent: Tuesday, July 16, 2019 6:45 AM To: nvaccess/nvda <nvda@noreply.github.com> Cc: Joseph Lee <joseph.lee22590@gmail.com>; Comment <comment@noreply.github.com> Subject: Re: [nvaccess/nvda] Launching a new copy of NVDA should exit running version and start launched version. (#8320) @JulienCochuyt <https://github.com/JulienCochuyt> has already written a PR for this--a month or so ago, and an update yesterday. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8320?email_source=notifications&email_token=AB4AXEAR6PQF2RS2W4KKCELP7XGEJA5CNFSM4FA7KHC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2A4RMI#issuecomment-511822001> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4AXECYJCKP557KW6QG62LP7XGEJANCNFSM4FA7KHCQ> .

[XLTechie]

Thanks

[josephsl]

Hi,

I'm going to reopen this to serve as a reminder as to the tough road ahead: see #10179 for a full explanation, as the design of this issue includes an unintended side effect for installed copy of NVDA when it comes out of secure screens.

Thanks.

[Adriani90]

A fix up for #10179 is provided in #10183. Thus, closing this one in favor of the both references. I suggest to reopen the feature requests only if the whole feature is implemented and reverted due to something. If there is only a bug due to the feature but the feature is not completely reverted, then I suggest to open new issues like in this case #10179. If there are more bugs discovered based on this feature, then we should think about reverting the whole feature and then we can reopen this one again.
Thanks.