-
-
Notifications
You must be signed in to change notification settings - Fork 631
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
No result reported in calculator #15923
Comments
Hi, A few things:
Thanks. |
Testing with same version of Calculator, but on Windows 23H2 (Build 22631.2861) and NVDA alpha-30306,7ed382b5 (2024.2.0.30306) As we can see, Braille announces correctly the result. |
The STR has no sense with numlock disabled, since you type the numbers and the operator on the numpad.
Yes, the issue is specific to NVDA.
Here it is: |
@ruifontes wrote:
Note that the part of the logfile that you have pasted here is using the numlock. Could you paste the same using the alphanumeric keyboard? Which keyboard localization are you using (in case it depends on localization) Note that I have tested with the following keyboard locales:
|
Keyboard in pt_PT, Portuguese (Portugal) IO - speech.speech.speak (16:16:33.350) - MainThread (11472): |
Hi, Affects Narrator as well. Here's why:
NVDA does handle UIA notification event. It's just that it doesn't know that a number key was entered prior to Enter being pressed, so the "no results announcement" state is not toggled correctly. However, as the above process shows, the fundamental issue is with Calculator itself not firing notification event if both operands around an operator are single digits. This problem is "resolved" if more than two operands are present. We can solve this in a number of ways:
Of these, I advise the third option, as options 1 and 2 can cause regressions and amount to fixing the problem at the surface level a.k.a. workaround, respectively. Postscript: I won't respond to this issue until next week at the earliest as I'm taking finals and to look into this matter from different angles. Thanks. |
@josephsl, as written in #15923 (comment), I have not the problem with Narrator.
Does it mean that you do not get the correct result with Narrator on your side? |
Hi, What I looked at is not just the result of what Narrator does (it does announce results, by the way), but the events that led to Narrator not announcing single digits between operators, which turned out to be UIA notification event problem from Calculator app itself. I think this is one of those cases where resolving it from screen readers is a short-term solution, with the actual issue coming from the app. Short of asking Calculator team (Microsoft) to look into this matter, if you do want NVDA side solution, please let us know. Thanks. |
Since you have identified an issue on the app side, I agree that it should be reported to Microsoft. Given you have the evidences that the app does not behave correctly, would you be able to report it to them? If you cannot, e.g. for lack of time, no worry. Just indicate it here as a status. Though, if possible, it would be nice to have a fix in NVDA in the meantime, given we do not know how much time it will take to Microsoft to fix the problem. |
Hi, As a temporary measure, I will include a fix for this issue in Windows App Essentials 24.01 until Microsoft fixes this. Thanks. |
@msftedad can you take this up with the development team please? It needs an external fix from microsoft side, particularly firing the correct UIA events. |
@Adriani90 - thank you for tagging us here, we will discuss and share this MS calculator Team and inform you with progress here. |
@Adriani90 - This case is forwarded to MS calculator team. |
Not to be confused with #15918
Steps to reproduce:
Actual behavior:
No result is reported when NumpadEnter is pressed.
Expected behavior:
The result should be reported with NumpadEnter.
NVDA logs, crash dumps and other attachments:
None
Notes
Maybe the issue is linked to the algorithm used to filter UIA notifications.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2023.3
Windows version:
Windows 10 22H2 (AMD64) build 19045.3693
Name and version of other software in use when reproducing the issue:
CalculatorApp.exe
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested
Cc @josephsl, @ruifontes
The text was updated successfully, but these errors were encountered: