-
-
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
Problems with command consoles and object navigation #673
Comments
Comment 1 by jteh on 2010-09-23 02:59 |
Comment 2 by jteh (in reply to comment description) on 2010-11-09 09:17
This is fixed in the update to make consoels use the Terminal behavior in the displayModelNewText branch.
This still happens even with the above fix, but it doesn't really matter because it isn't monitored for new text. The final issue is still unsolvable, as noted earlier. |
@jcsteh: Can't we tie console connect/disconnect to event_gainFocus/leaveFocus? |
Sure we can. However, that will make it impossible to review non-focused consoles. Still, that's probably the best we can hope for at this stage, so that's probably the solution we should go with. |
Any update on this? |
cc: @derekriemer |
Once #9771 is merged, this issue will be resolved on Windows 10 version 1803 and later; UIA has no notion of "connecting" to consoles like the legacy support did. However, it is still not fixed on Windows Server and LTSC 2016 (Windows 10 1607), which will still be supported for many years to come. Unfortunately though, since the legacy console support requires that we connect to consoles in this way, we cannot fix the bug on this older release. Since the issue has either been resolved or resolution is impossible, I vote to close it. You are, of course, welcome to investigate further for legacy consoles and propose a solution if one exists! |
… 1803 and later (PR #9771) NVDA's UIA console support significantly improves performance and stability, so we should enable it by default. While UIA in consoles was added in Windows 10 1709, the initial implementation left much to be desired, particularly concerning caret movement and expansion to character. A new `UIAUtils.shouldUseUIAConsole` function has been added which determines whether to use UIA in consoles: * If the user has explicitly chosen to use UIA or legacy console support, the function returns `True` or `False` respectively. * Otherwise, if the user is running at least Windows 10 1803, the function returns `True`, or `False` if not. The "use UI Automation in the Windows Console when available" GUI setting has been changed to expose all options in the config spec (i.e. to automatically detect UIA/legacy or override this autodetection). builds on #9614 closes #673 closes #6291
Reported by jteh on 2010-05-26 22:41
When you move to a command console with object navigation, NVDA connects to this console, which allows this console to be reviewed. While this is useful, it presents three problems:
While issues 1 and 2 can be fixed, it is probably not possible to solve issue 3, as this is due to a limitation of the implementation in Windows. Therefore, the only option may be to not connect to consoles for review.
Work around: To restore functionality to a focused console, move the navigator object back to the focused console.
This functionality was introduced in 4808ab6.
The text was updated successfully, but these errors were encountered: