Adding command gesture categories for appmodules#15867
Conversation
…randa32, and vipmud
See test results for failed build of commit 6cc0250e20 |
CyrilleB79
left a comment
There was a problem hiding this comment.
Welcome Nael and congratulation for your first PR.
Here is my review:
|
@Nael-Sayegh welcome to NVDA development and thank you so much for this great work.
|
|
Thank you for your encouragement and advice. What do you think of my modifications? |
See test results for failed build of commit b96c123820 |
CyrilleB79
left a comment
There was a problem hiding this comment.
OK. My bad for the category name...
Also, there are still linting errors.
Makes sense for shift+F2: even if it uses the same shortcut as a native Excel command, it is a specific NVDA command, documented in the User Guide and that can be remapped. @Nael-Sayegh, the script is in For NVDA+shift+H in Word, I do not agree to add it a category, nor to do anything in this PR. First as written by @Nael-Sayegh because it has no description. Second, if your proposal is to add a description too, this is not enough, since the script causes an error when not in table and more things needs to be discussed on this script (see #11465). Today, my personal opinion is that this debug script should be removed completely and a new command should be implemented from scratch to report useful information in a table if needed (see #3462 and more specifically #3462 (comment)). But anyway this should first be discussed and then be implemented in another PR. |
|
@CyrilleB79 Thank you, I have made the necessary changes, this time it should be good. |
|
@CyrilleB79 Sorry, I didn't see your response about Excel. I'm going to take a look and try to add it to a category. |
|
I added the Excel category to the command gestures. |
See test results for failed build of commit f5a9099100 |
|
No, it's a mistake, my IDE added it automatically and I didn't notice. Thank you for pointing it out, I've made the corrections. |
|
Looking at the Excel scripts that have been modified for Excel, I realize that Word equivalent scripts (set row/column headers and read comment) should also be categorized. Finally, it makes me think that categorizing Excel and Word script in "Excel" and "Word" categories is not a good idea. The Poedit scripts are specific to an application and it makes sense to have a category for this application. In the case of Word/Excel, the scripts are more general:
Do you agree with this suggestion? |
|
@CyrilleB79 I agree with you on the comment, but then, what would be the shortcuts to put in the system caret? |
I was thinking to use That's just a proposal and other people may disagree with me; to be discussed... |
There was a problem hiding this comment.
Looks good to me, even if @CyrilleB79 raised some points which would deserve to be discussed. Maybe on a separate PR?
And please read the other review made about script not to be remapable.
|
Okay, I think the discussion should be in a separate PR or issue because it's no longer entirely on topic for this issue. |
|
Please put "fixes" or "closes" before the issue number in your PR description, so that the issue is automatically linked |
See test results for failed build of commit 5c25c1bf96 |
See test results for failed build of commit 4f5ba7ddf7 |
See test results for failed build of commit c9d1bc94e9 |
|
Hello, |
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
See test results for failed build of commit 5cad186961 |
See test results for failed build of commit 65640b96b6 |
|
Hello, |
|
There is also the nvda+o gesture for Microsoft Excel when using UIA for Excel, which displays in a browseable window useful information about the cell. This gesture is not documented in the user guide. See also #14082. |
|
@Adriani90, as explained in #14082, the status of NVDA+O is not clarified. Since Excel UIA is experimental and since NVDA+O appears to be a demo script, there is no point in adding it in the current PR. When it is decided what should be done with NVDA+O in #14082, it is still time either to remove it completely or to document it in input gesture dialog, input help and user guide, as well as adapt it to other situations, at least Excel legacy. |
) I have put various little changes in the same PR. Let me know if I should divide it. Link to issue number: Follow-up of #15867. Summary of the issue: Various issues seen in #15867 or while investigating on it (e.g. looking at usages of gesture.send()): Script BrowseModeTreeInterceptor.script_passThrough in browseMode.py has a description. It should not since: 1. It is only dedicated to specific key which should not be remapped; 2. There should not be any input help associated to it, since this "pass through" should be transparent to users. In Eclipse, when no selected auto-completion item can be found, NVDA+D should not pass the gesture through. Indeed gesture.send() should not be used since NVDA+D is not a native gesture of this IDE. An error message should be reported instead. The PowerPoint script does not show up in its category, whereas it was the goal in Adding command gesture categories for appmodules #15867. With 15867, scripts to set headers of rows or columns in Excel or Word have their description shortened and the details of its usage (e.g. 1 press, 2 presses) is not reported anymore in input help. This is not consistent with other scripts. It's better to keep more details in input help as for other scripts.
…ion (nvaccess#15906) I have put various little changes in the same PR. Let me know if I should divide it. Link to issue number: Follow-up of nvaccess#15867. Summary of the issue: Various issues seen in nvaccess#15867 or while investigating on it (e.g. looking at usages of gesture.send()): Script BrowseModeTreeInterceptor.script_passThrough in browseMode.py has a description. It should not since: 1. It is only dedicated to specific key which should not be remapped; 2. There should not be any input help associated to it, since this "pass through" should be transparent to users. In Eclipse, when no selected auto-completion item can be found, NVDA+D should not pass the gesture through. Indeed gesture.send() should not be used since NVDA+D is not a native gesture of this IDE. An error message should be reported instead. The PowerPoint script does not show up in its category, whereas it was the goal in Adding command gesture categories for appmodules nvaccess#15867. With 15867, scripts to set headers of rows or columns in Excel or Word have their description shortened and the details of its usage (e.g. 1 press, 2 presses) is not reported anymore in input help. This is not consistent with other scripts. It's better to keep more details in input help as for other scripts.
Link to issue number:
closes #15815
Summary of the issue:
Store the Poedit, PowerPoint, miranda32, vipmud, and Eclipse appModules in separate categories within the command gesture category.
Description of user facing changes
When the user is in one of the applications (poedit, powerpoint, eclipse, vipmud, and miranda32), and if they wish to view the keyboard shortcuts offered by the appmodule, they can consult them in the command gesture category under the section named after the application rather than in various.
Description of development approach
I have added in each appmodule a variable that contains the name of the category, and for each keyboard shortcut, I have added the name of the category associated with that command.
Testing strategy:
I tested each application by opening the app and checking if the corresponding category appeared in NVDA's command gestures.
Known issues with pull request:
Code Review Checklist: