Skip to content
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

When the system scaling is set to something other than 100% (e.g. 200%), the position of the tree item's NVDAObject in Regedit's tree control does not match the actual position. #17709

Open
hwf1324 opened this issue Feb 18, 2025 · 0 comments
Labels
app-specific audience/low-vision PR or issue is relevant to sighted or low vision users needs-technical-investigation A technical investigation is required to progress the issue. p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@hwf1324
Copy link
Contributor

hwf1324 commented Feb 18, 2025

Steps to reproduce:

  1. Windows+R Open the Run dialog box, type regedit and enter.
  2. Move your mouse over the tree item in the tree control or navigate to the tree item.

Actual behavior:

The position of the tree item's NVDAObject does not correspond to its actual position, which especially affects mouse tracking.

It can be determined by OCR

Expected behavior:

The location of the tree item's NVDAObject should match the actual location.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

install

NVDA version:

alpha-35319,a1a2bc00

Windows version:

Windows 11 Version 24H2 (OS Build 26100.3194)

Name and version of other software in use when reproducing the issue:

regedit Version 24H2 (OS Build 26100.3194)

Other information about your system:

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.

Yes

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?

Yes

@gerald-hartig gerald-hartig changed the title When the system scaling is set to something other than 100% (e.g. 200%), the position of the tree item's NVDAObject in egedit's tree control does not match the actual position. When the system scaling is set to something other than 100% (e.g. 200%), the position of the tree item's NVDAObject in regedit's tree control does not match the actual position. Feb 24, 2025
@gerald-hartig gerald-hartig added p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. needs-technical-investigation A technical investigation is required to progress the issue. app-specific audience/low-vision PR or issue is relevant to sighted or low vision users labels Feb 24, 2025
@SaschaCowley SaschaCowley changed the title When the system scaling is set to something other than 100% (e.g. 200%), the position of the tree item's NVDAObject in regedit's tree control does not match the actual position. When the system scaling is set to something other than 100% (e.g. 200%), the position of the tree item's NVDAObject in Regedit's tree control does not match the actual position. Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app-specific audience/low-vision PR or issue is relevant to sighted or low vision users needs-technical-investigation A technical investigation is required to progress the issue. p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

2 participants