-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
Refocus multi-category settings dialog with the provided category. #12995
base: master
Are you sure you want to change the base?
Conversation
This PR is a follow-up of #12800.
|
With #12944 closed, are the testing steps in 4 still an issue? Can you merge in master and reconfirm testing? |
I have updated merging the latest master branch. Regarding test 4, I can add that step 3. is actually not mandatory and can be ignored. For now, I still do not know how to solve step 4. If you have any advice, let me know. @seanbudd let me know if I should keep this issue as a draft or not. |
I think in absence of a solution for test 4, this PR is still an improvement of behaviour. |
No @seanbudd, I do not consider this PR as is as an improvement due to the following result which is not acceptable IMO:
This is a new and concerning issue introduced by this PR, since NVDA+Tab incorrectly reports that the change button has the focus, whereas this button is not displayed anymore. Would you have any hint to implement one of the suggestions made in #12995 (comment)? |
I spent some time investigating this a couple of weeks ago and hit dead ends unfortunately. |
@CyrilleB79 i was looking at nvda's pull request history, and looked at this, even tho i've looked at this several times before. This is really interesting, any update about this? or you stil don't have any ideas of fixing the mentioned issues and make this ready? I'd like to try this as whel, can you please trigger the ap veyor build by merging the master? or it is currently impossible? thanks. |
@CyrilleB79 regarding the problem of opening select sinthesizer dialog causes a bug for refocusing the provide catigory in the settings dialog, i have a good, standard and easy idea. My idea is: |
guys, was my idea sound good and helpful for you in this repo? |
hi
|
@amirmahdifard and @HanaDadfar, actually, if you wish to discuss the benefit of having speech synth dialog accessible either directly or through the Speech settings dialog, I'd recommend to do it in a separate issue.
BTW @amirmahdifard, regarding re-triggering the appVeyor build, as already told in another issue, I cannot do it unless I also fix the conflicts. Moreover I have encouraged you to install and debug your own local build setup, with help from nvda-devel mailing list if needed, but have not seen any news from you on that list. |
@CyrilleB79 |
Hi Cyrille, I noticed there's been some recent movement here, should this PR be kept open? |
Quite low priority for me, but I'd like to try a solution based on something similar to the blocking decorator when a setting dialog is already opened. |
@CyrilleB79 - do you plan to do any further work here? Otherwise this should be closed |
Link to issue number:
Fix-up of #12800.
Described in #12800 (comment), paragraph "Test almost successful", "Test 1".
Summary of the issue:
If the multi-category settings dialog is already opened and you try to open it a second time, it will be refocused. But the new expected category panel is not shown; the old panel remains shown instead.
Description of how this pull request fixes the issue:
Change the panel when refocusing a MultiCategorySettingsDialog according to the panel passed as parameter.
Testing strategy:
Test 1:
Press successively NVDA+control+G, NVDA+control+O, NVDA+control+M, NVDA+control+K.
Checked that the expected panel is shown each time.
Test 2:
Test 3:
Press NVDA+Control+K, Alt+Tab to Windows Explorer (or whatever), open NVDA menu -> Preferences -> Settings.
Settings dialog is refocused on keyboard settings panel.
Test 4:
Result:
I think that this last point should be resolved before merging this PR.
All tests are successful except test 4.
Known issues with pull request:
None
Code Review Checklist: