Steps to reproduce:
- Install NVDA-Alpha-28685
- Install "Instant Translate" or "UnigramPlus" add-on.
- Restart NVDA
Actual behavior:
The add-on failed to load because the settings panel failed to initialize.
Try typing from gui import SettingsPanel in the NVDA Python console and execute it.
Traceback (most recent call last):
File "<console>", line 1, in <module>
ImportError: cannot import name 'SettingsPanel' from 'gui' (C:\Program Files (x86)\NVDA\library.zip\gui\__init__.pyc)
Expected behavior:
Add-on compatibility should not be broken
NVDA logs, crash dumps and other attachments:
log.txt
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA-Alpha-28685
Windows version:
Windows 10 22H2 (AMD64) build 19045.3155
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
None
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.
alpha-28675 can't reproduce this, I suspect it's a regression of #15121.
If NVDA add-ons are disabled, is your problem still occurring?
No
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Steps to reproduce:
Actual behavior:
The add-on failed to load because the settings panel failed to initialize.
Try typing
from gui import SettingsPanelin the NVDA Python console and execute it.Expected behavior:
Add-on compatibility should not be broken
NVDA logs, crash dumps and other attachments:
log.txt
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA-Alpha-28685
Windows version:
Windows 10 22H2 (AMD64) build 19045.3155
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
None
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.
alpha-28675 can't reproduce this, I suspect it's a regression of #15121.
If NVDA add-ons are disabled, is your problem still occurring?
No
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes