{"action":"created","issue":{"url":"https://api.github.com/repos/nvaccess/nvda/issues/5585","labels_url":"https://api.github.com/repos/nvaccess/nvda/issues/5585/labels{/name}","comments_url":"https://api.github.com/repos/nvaccess/nvda/issues/5585/comments","events_url":"https://api.github.com/repos/nvaccess/nvda/issues/5585/events","html_url":"https://github.com/nvaccess/nvda/issues/5585","id":120553771,"number":5585,"title":"Copy Current Configuration to Secure Screens: Add Remove button to General Settings Dialog","user":{"login":"elliott94","id":15790146,"avatar_url":"https://avatars.githubusercontent.com/u/15790146?v=3","gravatar_id":"","url":"https://api.github.com/users/elliott94","html_url":"https://github.com/elliott94","followers_url":"https://api.github.com/users/elliott94/followers","following_url":"https://api.github.com/users/elliott94/following{/other_user}","gists_url":"https://api.github.com/users/elliott94/gists{/gist_id}","starred_url":"https://api.github.com/users/elliott94/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/elliott94/subscriptions","organizations_url":"https://api.github.com/users/elliott94/orgs","repos_url":"https://api.github.com/users/elliott94/repos","events_url":"https://api.github.com/users/elliott94/events{/privacy}","received_events_url":"https://api.github.com/users/elliott94/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-12-05T13:18:36Z","updated_at":"2015-12-07T02:41:45Z","closed_at":null,"body":"Currently, NVDA allows a user to copy their settings to the systemConfig directory of NVDA's install location; this process can easily be achieved by simply activating the relevant button from within the General Settings dialog.\r\n\r\nWhilst this function works as expected, unless the user is somewhat advanced an option does not currently exist that easily allows the removal of these settings. I can think of two possible ways of easily implementing this (starting with the preferred):\r\n\r\n1. Keep a single button in the General Settings dialog, and change it's title to \"Add/remove currently saved settings on the logon and other secure screens (requires administrator privileges)\". When activated, NVDA would search for the existence of the systemConfig directory, and depending on the result either copy the user's current settings as is currently done, or prompt the user as to whether they are sure that they wish for the directory to be removed.\r\n\r\n2. When the user first chooses to copy their current settings, a value could be inserted within NVDA's configuration file; upon launching, NVDA would search for the existence of this value, and depending on the result carry out a different action when the button is pressed from within General Settings. The downside of this method is that in theory, a user could manually remove the systemConfig directory themselves, and as a result the value within nvda.ini has the potential to be out-of-date and not reflect the current state of the directory."},"comment":{"url":"https://api.github.com/repos/nvaccess/nvda/issues/comments/162393575","html_url":"https://github.com/nvaccess/nvda/issues/5585#issuecomment-162393575","issue_url":"https://api.github.com/repos/nvaccess/nvda/issues/5585","id":162393575,"user":{"login":"jcsteh","id":4166475,"avatar_url":"https://avatars.githubusercontent.com/u/4166475?v=3","gravatar_id":"","url":"https://api.github.com/users/jcsteh","html_url":"https://github.com/jcsteh","followers_url":"https://api.github.com/users/jcsteh/followers","following_url":"https://api.github.com/users/jcsteh/following{/other_user}","gists_url":"https://api.github.com/users/jcsteh/gists{/gist_id}","starred_url":"https://api.github.com/users/jcsteh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcsteh/subscriptions","organizations_url":"https://api.github.com/users/jcsteh/orgs","repos_url":"https://api.github.com/users/jcsteh/repos","events_url":"https://api.github.com/users/jcsteh/events{/privacy}","received_events_url":"https://api.github.com/users/jcsteh/received_events","type":"User","site_admin":false},"created_at":"2015-12-07T02:41:45Z","updated_at":"2015-12-07T02:41:45Z","body":"What's the use case for this? Presumably, most users might want the system config to reflect their current config, but i can't see a good reason for them to want to revert it to the default configuration. One reason would be if their configuration was broken, but in that case, their user configuration would also be broken, in which case they would fix their own config and then copy it again.\r\n\r\nIMO, \"Add currently saved settings on the logon and other secure screens\" doesn't make a huge amount of sense. Remove is even worse because they're not technically removing *current* settings; they're removing what was there, which might be very different settings."}}