davidacm / NVDA-IBMTTS-Driver

This project is aimed at developing and maintaining the NVDA IBMTTS driver. IBMTTS is a synthesizer similar to Eloquence. Please send your ideas and contributions here!
GNU General Public License v2.0
56 stars 23 forks source link

IBMTTS no longer appears in NVDA's Settings dialog #93

Closed amirsol81 closed 1 year ago

amirsol81 commented 1 year ago

With NVDA Alpha V28351 and above, IBMTTS no longer appears in NVDA's Settings window. It means that we can no longer alter the library location or modify certain settings related to the driver itself. The driver itself functions properly as far as TTS performance is concerned.

ultrasound1372 commented 1 year ago

That would be because of this error.

ERROR - globalPluginHandler.listPlugins (09:54:28.234) - MainThread (17256):
Error importing global plugin ibmtts
Traceback (most recent call last):
  File "globalPluginHandler.pyc", line 23, in listPlugins
  File "importlib\__init__.pyc", line 127, in import_module
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "C:\Users\Colton\AppData\Roaming\nvda\addons\IBMTTS\globalPlugins\ibmtts.py", line 14, in <module>
    from ._ibmttsUtils import UpdateHandler, GithubService, guiCopiFiles
  File "C:\Users\Colton\AppData\Roaming\nvda\addons\IBMTTS\globalPlugins\_ibmttsUtils.py", line 14, in <module>
    from gui.addonGui import _showAddonRequiresNVDAUpdateDialog, _showAddonTooOldDialog, promptUserForRestart
ImportError: cannot import name '_showAddonTooOldDialog' from 'gui.addonGui' (C:\Program Files (x86)\NVDA\library.zip\gui\addonGui.pyc)

I'm unsure if that dialog still exists and is just in the store module now or is actually gone entirely, so I'm unsure of a cross-version way to handle this. And that appears to be an internal function by the leading underscore so they don't even need to say it's an API breaking change.