-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
Screen curtain is not working on newer windows insider builds #12491
Comments
@feerrenrut |
Hi, or rather, hope it gets resolved before Version 21H2 (Cobalt) ships to release preview Insiders provided that 21H2 is build 21000 or later. Thanks.
|
I'm curious to know:
|
More specifically, does the color inversion feature work correctly? I think that it uses the same color transformation matrix API as the screen curtain. |
True. Actually, we're using the same API and making the screen black this way. May be transforming to another color does still work. |
Please find comments inline
|
I've reproduced this using windows build 21390.1. The screen curtain causes the screen to freeze, i.e. no longer visually update, but is otherwise visible. As this is an insiders issue, and likely an unintended bug that will be fixed by Microsoft before a stable Windows version is shipped, we think it's best to delay looking at this until it has been around for a while but before 2021.2 is released. |
This is also confirmed to be an issue with the Windows 11 insider build (22000.65) |
I don't necessarily agree. While it is true that this is likely an unintended bug by Microsoft, I think it's still a good idea to at least track down what's causing the bug. Microsoft has a bit of a track record of taking quite a bit of time to fix unintended bugs at times, so if this is broken in insiders both for windows 10 and Windows 11, and we don't actually know what is causing this to happen, we can't report appropriate feedback either, which may very well mean this does not in fact get fixed on its own. |
Hi, I think it would be best to rename this issue to point out that this is a Windows 11 issue. Re: #12585 collection |
Link to issue number: Fix for #12491 Summary of the issue: Screen curtain does not work as intended for new Windows builds. This is due to an API change. Previously, NVDA used a fully transparent colour transformation to create the screen curtain, which now no longer results in a black screen. In the future, the API is unstable: "The Magnification API is not supported under WOW64; that is, a 32-bit magnifier application will not run correctly on 64-bit Windows.". Description of how this pull request fixes the issue: Implements the screen curtain with a fully solid opacity. Adds a warning to test newer Windows builds when using screen curtain. Testing strategy: Test starting screencurtain using this PR build on a Windows 10 insiders build Test starting screencurtain using this PR build on a Windows 11 insiders build Test starting screencurtain using this PR build on a Windows 10 stable build Test starting screencurtain using this PR build on a Windows 8 stable build Known issues with pull request: This may occur again in the future due to the API not being fully supported, or another undefined behaviour change like this one. It would be good to add a test that confirms the screen is black using an independent tool, and/or move towards a different API.
Steps to reproduce:
Actual behavior:
When we turn on the screen curtain, nothing happens. although, NVDA reports like: "Temporary screen curtain, enabled untill next restart" but screen still stays as before and doesn't turn black.
Expected behavior:
Screen curtain should work.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
Version: alpha-22960,34e831bb
Windows version:
Windows 10 (Insider) build 21390
Name and version of other software in use when reproducing the issue:
NA
Other information about your system:
NA
Other questions
Does the issue still occur after restarting your computer?
Yes, always
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes, tried from 2020.4 to latest alpha, but no luck
If 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?
Yes
The text was updated successfully, but these errors were encountered: