Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixup 'Temporary Copy restrictions' in the user guide #15222

Merged
merged 2 commits into from
Jul 31, 2023
Merged

Fixup 'Temporary Copy restrictions' in the user guide #15222

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eddadb6
Fixup 'Temporary Copy restrictions' in the user guide
seanbudd Jul 30, 2023
a844006
fix up phrasing
seanbudd Jul 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions user_docs/en/userGuide.t2t
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,9 +347,13 @@ The installed copy is also able to create a portable copy of itself at any time.
The portable copy also has the ability to install itself on any computer at a later time.
However, if you wish to copy NVDA onto read-only media such as a CD, you should just copy the download package.
Running the portable version directly from read-only media is not supported at this time.
Using the temporary copy of NVDA is also an option (e.g. for demonstration purposes), though starting NVDA in this way each time can become very time consuming.

Apart from the inability to automatically start during and/or after log-on, the portable and temporary copies of NVDA also have the following restrictions:
The [NVDA installer #StepsForRunningTheDownloadLauncher] can be used as a temporary copy of NVDA.
Temporary copies prevent saving NVDA configuration such as settings or input gestures.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@seanbudd, @Qchristensen, that is not true (at least for NVDA 2023.2beta1).
Indeed, modifying the gestures is allowed while running temp version of NVDA.

I think that the idea was to prevent writing on disk in temp versions only if it might cause issue with the installed version. E.g.: writing the config the config (settings) on the disk is not allowed because the config scheme (version) may be different and incompatible between installer and installed version. On the contrary writing gestures from a newer version does not cause any problem to older version: non-existing scripts are just silently ignored by the older version. If NVAccess changes the behaviour, it should be clarified and the reasons of it should be explained to developers.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been fixed up in #15248

Note that the intention was actually to prevent any config from being saved to disk, as NVDA should be treated as a fully temporary copy in this case. This will be addressed in 2023.3 with more clear restrictions around secure screens, and temporary copies

This includes blocking usage of the [Add-on Store #AddonsManager].

Portable and temporary copies of NVDA have the following restrictions:
- The inability to automatically start during and/or after log-on.
- The inability to interact with applications running with administrative privileges, unless of course NVDA itself has been run also with these privileges (not recommended).
- The inability to read User Account Control (UAC) screens when trying to start an application with administrative privileges.
- Windows 8 and later: the inability to support input from a touchscreen.
Expand Down