Link to issue number:

None

Summary of the issue:

When running nvda from sources using a relative path such as pythonw source\nvda.pyw NVDA failed to restart. This was caused by the fact that shellapi.ShellExecute executes given process using cwd as the directory from which the given command should be running and when NVDA starts it changes cwd to its own source directory.

Description of how this pull request fixes the issue:

When restarting NVDA globalVars.appdir is used as a directory from which new process should be started. While at it I've also made the restart code more compact by removing unneeded parameters from sys.argv. in a loop.

Testing performed:

with NVDA repository at d:\my_repos\nvda started NVDA with the following invocations and ensured it can be restarted successfully:

• pythonw nvda.pyw from the source directory
• pythonw source\nvda.pyw from the main directory of the repo

I've also ensured that binary version of NVDA can be restarted successfully with these changes.

Known issues with pull request:

None known

Change log entry:

I don't think changelog entry is needed here - this would affect only developers and this issue was present for a long time.