-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
GUI: Consider only allowing a single dialog to be displayed at once upon initial config creation #11679
Comments
One of the issues I get is an add on update and a program update occur
almost at the same time, and whichever one actions, the other one will not
return, since you are restarting nvda. Sometimes though the add on one does
attempt to come up at restart but nvda can fall over for some reason.
Its a pity some kind of precedence could not be used here before confusing
the user with two dialogues.
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "elliott94" <notifications@github.com>
To: "nvaccess/nvda" <nvda@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>
Sent: Sunday, September 27, 2020 11:21 AM
Subject: [nvaccess/nvda] GUI: Consider only allowing a single dialog to be
displayed at once upon initial config creation (#11679)
… <!-- Please read the text in this edit field before filling it in.
Please thoroughly read NVDA's wiki article on how to fill in this
template, including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
Please also note that the NVDA project has a Citizen and Contributor Code
of Conduct which can be found at
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.MD. NV Access
expects that all contributors and other community members read and abide
by the rules set out in this document while participating or contributing
to this project. This includes creating or commenting on issues and pull
requests.
-->
### Is your feature request related to a problem? Please describe.
When NVDA initially creates its configuration under a user account that
has no existing configuration, depending on conditions it's possible to
potentially have three separate dialogs appearing on screen in quick
succession:
1. The initial Welcome dialog
2. The Update dialog
3. The Gather Usage Statistics prompt
For new users, the possibility of all these dialogs appearing at once has
the potential to be overwhelming. Could we possibly consider changing this
behaviour so that only a single dialog can appear on screen at once?
Logically, it'd probably make sense for the Welcome dialog to initially be
displayed, followed by the Usage Statistics prompt second, and finally the
result of an update check (if an update is found).
### Describe the solution you'd like
### Describe alternatives you've considered
### Additional context
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#11679
|
Duplicate of issue #9174. |
Thank you - closing as a duplicate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When NVDA initially creates its configuration under a user account that has no existing configuration, depending on conditions it's possible to potentially have three separate dialogs appearing on screen in quick succession:
The initial Welcome dialog
The Update dialog
The Gather Usage Statistics prompt
For new users, the possibility of all these dialogs appearing at once has the potential to be overwhelming. Could we possibly consider changing this behaviour so that only a single dialog can appear on screen at once? Logically, it'd probably make sense for the Welcome dialog to initially be displayed, followed by the Usage Statistics prompt second, and finally the result of an update check (if an update is found).
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: