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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks Sean!
|
||
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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
Can somebody translate this into what it actually means? I always update a portable copy as I do an installed on, to give me a fool proof way to reinstall nvda with the add ons I use. Does this mean one cannot do that any more, or have I missed something along the way. It also seems to preserve profiles if I mark this correctly in the settings as I make both an installed copy from a portable or vice versa. Of course we know that portable versions have restrictions, but I've so far not seen this one.
Brian
…--
***@***.***
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
***@***.***, putting 'Brian Gaff'
in the display name field.
|
@Brian1Gaff, you are making a confusion between portable and temporary copy. As indicated more explicitly in the documentation just modified in this PR:
Thus the temporary copy of NVDA is not a portable one, but just the instance of NVDA executing when you launch the installer. |
Link to issue number:
None
Summary of the issue:
#13985 introduced new restrictions for temporary copies of NVDA, preventing the add-on store from opening and preventing writing to disk.
These should be explained in the user guide
Description of user facing changes
N/A
Description of development approach
Simplified some of the structure in the user guide, including explaining what a temporary copy is.
Code Review Checklist: