Re: Driver MB408 velocizzato


sergio brunetti
 

Ciao Alberto. Ho installato il driver nella portable precedente all'ultima versione. Riavviato nvda come di consueto, la barra si è avviata.

E' possibile che una dll o qualche componente che serveper il funzionamento del bluetooth sia corrotto nel nuovo addon?

Ecco il log:

INFO - __main__ (12:09:36.657):
Starting NVDA
INFO - core.main (12:09:36.970):
Config dir: D:\nvda portable\userConfig
INFO - config.ConfigManager._loadConfig (12:09:36.970):
Loading config: .\userConfig\nvda.ini
INFO - core.main (12:09:37.236):
NVDA version 2019.2
INFO - core.main (12:09:37.236):
Using Windows version 10.0.17763 workstation
INFO - core.main (12:09:37.236):
Using Python version 2.7.16 (v2.7.16:413a49145e, Mar  4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)]
INFO - core.main (12:09:37.236):
Using comtypes version 1.1.7
INFO - core.main (12:09:37.236):
Using configobj version 5.1.0 with validate version 1.0.1
ERROR - synthDriverHandler.setSynth (12:09:37.463):
setSynth
Traceback (most recent call last):
  File "synthDriverHandler.pyo", line 101, in setSynth
  File "synthDriverHandler.pyo", line 74, in getSynthInstance
  File "synthDriverHandler.pyo", line 41, in _getSynthDriver
ImportError: No module named eloquence
INFO - synthDriverHandler.setSynth (12:09:37.549):
Loaded synthDriver oneCore
INFO - core.main (12:09:37.549):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (12:09:37.549):
Braille input initialized
INFO - braille.initialize (12:09:37.549):
Using liblouis version 3.10.0
INFO - external:brailleDisplayDrivers.mb248.BrailleDisplayDriver.__init__ (12:09:37.663):
MDV using port *COM10*
INFO - external:brailleDisplayDrivers.mb248.BrailleDisplayDriver.__init__ (12:09:37.663):
try MDV using port COM10 at baud 38400
INFO - external:brailleDisplayDrivers.mb248.BrailleDisplayDriver.__init__ (12:09:39.315):
FOUND MDV using port COM10
INFO - braille.BrailleHandler.setDisplayByName (12:09:39.322):
Loaded braille display driver mb248, current display has 24 cells.
WARNING - core.main (12:09:39.648):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:09:39.664):
UIAutomation: IUIAutomation6
INFO - core.main (12:09:39.934):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (12:09:52.191):
Developer info for navigator object:
name: u'MB248driver.NVDA-addon'
role: ROLE_LISTITEM
states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_UIItemListItemUIA object at 0x0493A090>
Python class mro: (<class 'NVDAObjects.Dynamic_UIItemListItemUIA'>, <class 'NVDAObjects.UIA.UIItem'>, <class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=286, top=957, width=598, height=22)
value: ''
appModule: <'explorer' (appName u'explorer', process ID 5960) at address 48016f0>
appModule.productName: u'Sistema operativo Microsoft\xae Windows\xae'
appModule.productVersion: u'10.0.17763.769'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 329254
windowClassName: u'DirectUIHWND'
windowControlID: 0
windowStyle: 1442840576
extendedWindowStyle: 0
windowThreadID: 14592
windowText: u''
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0x92ee6e8 at 47aee90>
UIA automationID: 177
UIA frameworkID: DirectUI
UIA runtimeID: (5960, 442595024, 0)
UIA providerDescription: [pid:5960,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:explorerframe.dll)]
UIA className: UIItem
UIA patterns available: LegacyIAccessiblePattern, InvokePattern, ScrollItemPattern, SelectionItemPattern, ValuePattern

Il 20/02/2020 11:49, Alberto Buffolino ha scritto:
sergio brunetti, il 20/02/2020 08.59, ha scritto:
Concludo aggiongendo che neanche installando il componente nella portable versione precedente di nvda la barra parte. Funziona lì invece il driver della barra a 24 caratteri.
Alberto:
Ciao Sergio,
tutto ciò è quantomeno bizzarro.
Mi manderesti il log dopo aver collegato la barra con l'altro driver a 24 caratteri?
Grazie.
Alberto

Join nvda-it@groups.io to automatically receive all group messages.