Provide configurable developer scratchpad dir rather than automatic loading of custom code #9238
Link to issue number:
Summary of the issue:
Before add-ons, the only way to load custom appModules etc was to place them in a subdir of the NVDA user configuration directory. However, once add-ons became available, these subdires became deprecated in favor of add-ons.
Description of how this pull request fixes the issue:
NVDA no longer automatically loads code from subdires in NVDA's user configuration directory. Rather there is now a new option in the Advanced category of NVDA's settings dialog which enables loading of custom code from a Developer Scratchpad directory.
Started NVDA with a clean configuration. Verified that the scratchpad option was off, and no scratchpad directory existed.
Known issues with pull request:
There are going to be users who have old code in their user config dir which will no longer run without them checking it and moving it to the Developer scratchpad or packaging it as an add-on. It is strongly hoped that for code running day-to-day it will be packaged as an add-on. Developer scratchpad should only be used for developing code.
Change log entry:
The text was updated successfully, but these errors were encountered:
…es in the NVDA user configuration directory. Rather it will load tem from subdirectories in a new 'scratchpad' directory in the NVDA user configuration directory, but only if the open in the advanced category is enabled.
Hmm, I tended to use this idea to simply stop the nvda working for certain self voicing exe files. I am aware that you should be able to do much the same with profiles but I'm sure, like me there are a lot of old installations like mine which were long forgotten and just work. Brian firstname.lastname@example.org Sent via blueyonder. Please address personal E-mail to:- email@example.com, putting 'Brian Gaff' in the display name field. -----