Date   

Say all

Vlad Dragomir
 

Dear fellow users,

I hope someone will be able to tell me what I am doing wrong here.

I have a big .txt file, and I thought I would just sit back and ask NVDA to read it to me by pressing the usual command, insert+down arrow. Unfortunately after two or three paragraphs, the reading stops, and the cursor is still at the beginning of the file. If I go down with the arrow keys and find the place where it stopped reading, it does continue, but again only for about a minute, and it stops again. Once more, the cursor is where I left it.

Isn't it supposed to read the document until the end? Or at least until we stop it? I tried Notepad, QRead, even Notepad++. The behaviour is the same, so I presume I haven't configured NVDA correctly, but I can't guess which setting is to be modified.

Thank you very much for enlightening me on this. I'd love to be able to enjoy this book without having to go down line by line.

Warm regards,

vlad.


Re: NVDA and eclipse

Diego Ricardo Matos <diegoricardomatosm4@...>
 

Hello guys!
Could you send the email with what should happen to NVDA and swingset?
I was not on the list, and I did not find the topic.
Thank you.

Em 18/10/2018 12:01, Diego Ricardo Matos escreveu:

the java 8 32 bit is compatible with NVDA and access bridge, or I have
to install java 7?

2018-10-17 17:51 GMT-03:00, David Apps <david.apps@rnaanalytics.com>:
Dear Diego Ricardo Matos

Thank you for your message.

I have never used Eclipse, so I might be adding nothing helpful, sorry.

The page at the following address recommends installing both the 64-bit and
the 32-bit versions of the Java runtime environment on 64-bit Microsoft
Windows. I do not know whether this will help you, because the reason that
the page gives sounds as if it will not help you.

https://docs.oracle.com/javase/8/docs/technotes/guides/access/enable_and_test.html

" It is recommend[ed] that you install both the 32-bit and 64-bit versions
of the JRE. The 32-bit version only adds support for 32-bit assistive
technology, and the 64-bit version only adds support for 64-bit assistive
technology."

Have you tried any other Java application to confirm that the Java Access
Bridge is working properly? This page suggests using the SwingSet2.jar
application, which you can find in either jdk-8u191-windows-i586-demos.zip
or jdk-8u191-windows-x64-demos.zip available on the page at the following
address:

https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

When you have extracted the files in the zip archive, you should find the
SwingSet2 application: demo\jfc\SwingSet2\SwingSet2.jar

I sent a message to this list less than 24 hours ago describing the behavior
I experienced with the SwingSet2 application. Perhaps that would be useful
to you.

However, if you already know that the Java Access Bridge is working with
another Java Swing application, you need not worry about SwingSet2 at all.

I hope that this helps, but remember, I have never used Eclipse, so I might
be unintentionally wasting your time.

Thank you

David

________________________________

Notice of Confidentiality

This email is intended solely for the use of the individual or entity to
whom it is addressed and may be confidential. If you are not the intended
recipient, you must not disclose, reproduce, distribute or use this
information. Delivery of this message to any person other than the
individual or entity to whom it is addressed is not intended in any way to
waive confidentiality. If you have received this email in error please
notify the sender and delete the message immediately.

RNA Analytics is a limited liability company registered in England and
Wales, under registered number 10521383.
The registered address is: Ground Floor, Bancroft Place, 10 Bancroft Road,
Reigate, Surrey, RH2 7RP, United Kingdom

________________________________



Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Armando Maldonado
 


Hello, removing the braillenote add-on worked, thanks.
Armando

----- Original Message -----
From: Joseph Lee
Sent: Thursday, October 18, 2018 3:04 PM
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

Hi,

Ah, you might be running really old BrailleNote driver (not developed by me, but it served as a basis for current BrailleNote driver that ships with NVDA). What happens when you restart with add-ons disabled and connect to your Apex again? If that works, please uninstall the old BrailleNote add-on, as NVDA itself comes with BrailleNote support and the old driver has been deprecated for many years now.

P.S. This is one of those drivers/add-ons that we can’t guarantee Python 3 compatibility in the future. Once I officially return from vacation (next week at the earliest), I’ll start hunting for Python 3 issues and add-on compatibility problems again (and I really mean it).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Here you go.

INFO - __main__ (14:53:02.186):

Starting NVDA

INFO - core.main (14:53:02.688):

Config dir: C:\Users\Armando\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (14:53:02.688):

Loading config: C:\Users\Armando\AppData\Roaming\nvda\nvda.ini

INFO - core.main (14:53:02.713):

NVDA version 2018.3.2

INFO - core.main (14:53:02.713):

Using Windows version 10.0.17134 workstation

INFO - core.main (14:53:02.713):

Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]

INFO - core.main (14:53:02.713):

Using comtypes version 1.1.3

INFO - synthDriverHandler.setSynth (14:53:03.032):

Loaded synthDriver eloquence

INFO - core.main (14:53:03.032):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5

INFO - brailleInput.initialize (14:53:03.035):

Braille input initialized

INFO - braille.initialize (14:53:03.036):

Using liblouis version 3.6.0

INFO - braille.BrailleHandler.setDisplayByName (14:53:03.038):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (14:53:03.266):

UIAutomation: IUIAutomation5

INFO - core.main (14:53:03.757):

NVDA initialized

INFO - braille.BrailleHandler.setDisplayByName (14:53:06.142):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:15.144):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:15.144):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:20.137):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:20.137):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:35.447):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:35.448):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:40.167):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:40.167):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:44.522):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:44.522):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:47.928):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:47.928):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:50.154):

Error initializing display driver for kwargs {'port': u'COM1'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\baum.pyo", line 116, in __init__

RuntimeError: No Baum display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:50.154):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:00.888):

Error initializing display driver for kwargs {'port': u'COM1'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\baum.pyo", line 116, in __init__

RuntimeError: No Baum display found

INFO - braille.BrailleHandler.setDisplayByName (14:54:00.888):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:06.489):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:54:06.489):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:09.417):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:54:09.417):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:16.648):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:54:16.648):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:19.174):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:19.486):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:28.013):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:30.996):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:31.303):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:31.609):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:32.723):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:55:10.944):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:55:11.654):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:55:27.657):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:55:27.657):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:55:42.301):

Developer info for navigator object:

name: u'OK'

role: ROLE_BUTTON

states: STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.IAccessible.Button object at 0x049FA7B0>

Python class mro: (<class 'NVDAObjects.IAccessible.Button'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: RectLTWH(left=939, top=504, width=68, height=23)

value: None

appModule: <'nvda' (appName 'nvda', process ID 7972) at address 478ca90>

appModule.productName: u'NVDA'

appModule.productVersion: u'2018.3.2'

TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>

windowHandle: 526226

windowClassName: u'Button'

windowControlID: 0

windowStyle: 1342177281

windowThreadID: 6828

windowText: u'OK'

displayText: u'OK'

IAccessibleObject: <POINTER(IAccessible) ptr=0xb7afa70 at 48e3a30>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=526226, objectID=-4, childID=0

IAccessible accName: u'OK'

IAccessible accRole: ROLE_SYSTEM_PUSHBUTTON

IAccessible accState: STATE_SYSTEM_DEFAULT, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048836)

IAccessible accDescription: None

IAccessible accValue: None

 

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:45 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Okay, have you tried telling Windows 10 to forget your BrailleNote (Settings/Devices, then select your BrailleNote and remove) and pairing/connecting again? I think what might be happening is that NVDA might not be finding the BrailleNote at a designated Bluetooth COM port, or something else is going on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:34 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Ah, you might be running really old BrailleNote driver (not developed by me, but it served as a basis for current BrailleNote driver that ships with NVDA). What happens when you restart with add-ons disabled and connect to your Apex again? If that works, please uninstall the old BrailleNote add-on, as NVDA itself comes with BrailleNote support and the old driver has been deprecated for many years now.

P.S. This is one of those drivers/add-ons that we can’t guarantee Python 3 compatibility in the future. Once I officially return from vacation (next week at the earliest), I’ll start hunting for Python 3 issues and add-on compatibility problems again (and I really mean it).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Here you go.

INFO - __main__ (14:53:02.186):

Starting NVDA

INFO - core.main (14:53:02.688):

Config dir: C:\Users\Armando\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (14:53:02.688):

Loading config: C:\Users\Armando\AppData\Roaming\nvda\nvda.ini

INFO - core.main (14:53:02.713):

NVDA version 2018.3.2

INFO - core.main (14:53:02.713):

Using Windows version 10.0.17134 workstation

INFO - core.main (14:53:02.713):

Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]

INFO - core.main (14:53:02.713):

Using comtypes version 1.1.3

INFO - synthDriverHandler.setSynth (14:53:03.032):

Loaded synthDriver eloquence

INFO - core.main (14:53:03.032):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5

INFO - brailleInput.initialize (14:53:03.035):

Braille input initialized

INFO - braille.initialize (14:53:03.036):

Using liblouis version 3.6.0

INFO - braille.BrailleHandler.setDisplayByName (14:53:03.038):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (14:53:03.266):

UIAutomation: IUIAutomation5

INFO - core.main (14:53:03.757):

NVDA initialized

INFO - braille.BrailleHandler.setDisplayByName (14:53:06.142):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:15.144):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:15.144):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:20.137):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:20.137):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:35.447):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:35.448):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:40.167):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:40.167):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:44.522):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:44.522):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:47.928):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:47.928):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:50.154):

Error initializing display driver for kwargs {'port': u'COM1'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\baum.pyo", line 116, in __init__

RuntimeError: No Baum display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:50.154):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:00.888):

Error initializing display driver for kwargs {'port': u'COM1'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\baum.pyo", line 116, in __init__

RuntimeError: No Baum display found

INFO - braille.BrailleHandler.setDisplayByName (14:54:00.888):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:06.489):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:54:06.489):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:09.417):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:54:09.417):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:16.648):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:54:16.648):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:19.174):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:19.486):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:28.013):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:30.996):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:31.303):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:31.609):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:32.723):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:55:10.944):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:55:11.654):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:55:27.657):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:55:27.657):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:55:42.301):

Developer info for navigator object:

name: u'OK'

role: ROLE_BUTTON

states: STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.IAccessible.Button object at 0x049FA7B0>

Python class mro: (<class 'NVDAObjects.IAccessible.Button'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: RectLTWH(left=939, top=504, width=68, height=23)

value: None

appModule: <'nvda' (appName 'nvda', process ID 7972) at address 478ca90>

appModule.productName: u'NVDA'

appModule.productVersion: u'2018.3.2'

TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>

windowHandle: 526226

windowClassName: u'Button'

windowControlID: 0

windowStyle: 1342177281

windowThreadID: 6828

windowText: u'OK'

displayText: u'OK'

IAccessibleObject: <POINTER(IAccessible) ptr=0xb7afa70 at 48e3a30>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=526226, objectID=-4, childID=0

IAccessible accName: u'OK'

IAccessible accRole: ROLE_SYSTEM_PUSHBUTTON

IAccessible accState: STATE_SYSTEM_DEFAULT, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048836)

IAccessible accDescription: None

IAccessible accValue: None

 

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:45 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Okay, have you tried telling Windows 10 to forget your BrailleNote (Settings/Devices, then select your BrailleNote and remove) and pairing/connecting again? I think what might be happening is that NVDA might not be finding the BrailleNote at a designated Bluetooth COM port, or something else is going on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:34 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Armando Maldonado
 


Here you go.

INFO - __main__ (14:53:02.186):

Starting NVDA

INFO - core.main (14:53:02.688):

Config dir: C:\Users\Armando\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (14:53:02.688):

Loading config: C:\Users\Armando\AppData\Roaming\nvda\nvda.ini

INFO - core.main (14:53:02.713):

NVDA version 2018.3.2

INFO - core.main (14:53:02.713):

Using Windows version 10.0.17134 workstation

INFO - core.main (14:53:02.713):

Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]

INFO - core.main (14:53:02.713):

Using comtypes version 1.1.3

INFO - synthDriverHandler.setSynth (14:53:03.032):

Loaded synthDriver eloquence

INFO - core.main (14:53:03.032):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5

INFO - brailleInput.initialize (14:53:03.035):

Braille input initialized

INFO - braille.initialize (14:53:03.036):

Using liblouis version 3.6.0

INFO - braille.BrailleHandler.setDisplayByName (14:53:03.038):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (14:53:03.266):

UIAutomation: IUIAutomation5

INFO - core.main (14:53:03.757):

NVDA initialized

INFO - braille.BrailleHandler.setDisplayByName (14:53:06.142):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:15.144):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:15.144):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:20.137):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:20.137):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:35.447):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:35.448):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:40.167):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:40.167):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:44.522):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:44.522):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:47.928):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:53:47.928):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:53:50.154):

Error initializing display driver for kwargs {'port': u'COM1'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\baum.pyo", line 116, in __init__

RuntimeError: No Baum display found

INFO - braille.BrailleHandler.setDisplayByName (14:53:50.154):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:00.888):

Error initializing display driver for kwargs {'port': u'COM1'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\baum.pyo", line 116, in __init__

RuntimeError: No Baum display found

INFO - braille.BrailleHandler.setDisplayByName (14:54:00.888):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:06.489):

Error initializing display driver for kwargs {'port': 'bluetooth'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:54:06.489):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:09.417):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:54:09.417):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:54:16.648):

Error initializing display driver for kwargs {'port': u'COM5'}

Traceback (most recent call last):

File "braille.pyo", line 1659, in setDisplayByName

File "brailleDisplayDrivers\brailliantB.pyo", line 121, in __init__

RuntimeError: No display found

INFO - braille.BrailleHandler.setDisplayByName (14:54:16.648):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:19.174):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:19.486):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:28.013):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:30.996):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:31.303):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:31.609):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:54:32.723):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:55:10.944):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - braille.BrailleHandler.setDisplayByName (14:55:11.654):

Loaded braille display driver noBraille, current display has 0 cells.

ERROR - braille.BrailleHandler.setDisplayByName (14:55:27.657):

Error initializing display driver for kwargs {'port': 'auto'}

Traceback (most recent call last):

File "braille.pyo", line 1663, in setDisplayByName

File "extensionPoints\util.pyo", line 185, in callWithSupportedKwargs

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 134, in __init__

File "C:\Users\Armando\AppData\Roaming\nvda\addons\brailleNotDriver\brailleDisplayDrivers\brailleNote.py", line 167, in _describe

File "serial\serialwin32.pyo", line 295, in write

SerialTimeoutException: Write timeout

INFO - braille.BrailleHandler.setDisplayByName (14:55:27.657):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:55:42.301):

Developer info for navigator object:

name: u'OK'

role: ROLE_BUTTON

states: STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.IAccessible.Button object at 0x049FA7B0>

Python class mro: (<class 'NVDAObjects.IAccessible.Button'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: RectLTWH(left=939, top=504, width=68, height=23)

value: None

appModule: <'nvda' (appName 'nvda', process ID 7972) at address 478ca90>

appModule.productName: u'NVDA'

appModule.productVersion: u'2018.3.2'

TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>

windowHandle: 526226

windowClassName: u'Button'

windowControlID: 0

windowStyle: 1342177281

windowThreadID: 6828

windowText: u'OK'

displayText: u'OK'

IAccessibleObject: <POINTER(IAccessible) ptr=0xb7afa70 at 48e3a30>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=526226, objectID=-4, childID=0

IAccessible accName: u'OK'

IAccessible accRole: ROLE_SYSTEM_PUSHBUTTON

IAccessible accState: STATE_SYSTEM_DEFAULT, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048836)

IAccessible accDescription: None

IAccessible accValue: None

 

----- Original Message -----
From: Joseph Lee
Sent: Thursday, October 18, 2018 2:45 PM
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

Hi,

Okay, have you tried telling Windows 10 to forget your BrailleNote (Settings/Devices, then select your BrailleNote and remove) and pairing/connecting again? I think what might be happening is that NVDA might not be finding the BrailleNote at a designated Bluetooth COM port, or something else is going on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:34 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Can you try the following for me please:

  1. Try connecting to your Apex as a braille display (of course, following the prompts from KeySoft).
  2. When NVDA presents an error, press NVDA+F1, locate log viewer, then copy and paste the last few lines of the log viewer starting with “error – “ line. Please paste this info as a reply to my email so resident developers can find out what’s up.

For reference, I cannot reproduce this on my Windows 10 laptop running an equivalent of NVDA 2018.3 plus additional alpha-level code, and my Apex running KeySoft 9.5 connected to my laptop via Bluetooth.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, yes, I have and still get same error, thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:45 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Okay, have you tried telling Windows 10 to forget your BrailleNote (Settings/Devices, then select your BrailleNote and remove) and pairing/connecting again? I think what might be happening is that NVDA might not be finding the BrailleNote at a designated Bluetooth COM port, or something else is going on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:34 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Armando Maldonado
 


Hello, yes, I have and still get same error, thanks.

----- Original Message -----
From: Joseph Lee
Sent: Thursday, October 18, 2018 2:45 PM
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

Hi,

Okay, have you tried telling Windows 10 to forget your BrailleNote (Settings/Devices, then select your BrailleNote and remove) and pairing/connecting again? I think what might be happening is that NVDA might not be finding the BrailleNote at a designated Bluetooth COM port, or something else is going on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:34 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Okay, have you tried telling Windows 10 to forget your BrailleNote (Settings/Devices, then select your BrailleNote and remove) and pairing/connecting again? I think what might be happening is that NVDA might not be finding the BrailleNote at a designated Bluetooth COM port, or something else is going on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Armando Maldonado
Sent: Thursday, October 18, 2018 2:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----

From: Joseph Lee

Sent: Thursday, October 18, 2018 2:34 PM

Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Armando Maldonado
 


Hello, I am awer of automatic braille detection and it did not work for me, using winsows 10 andit's connecting via bluetooth. Thanks.

----- Original Message -----
From: Joseph Lee
Sent: Thursday, October 18, 2018 2:34 PM
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

 

Hi,

Apart from this news…

I’d like to know the following:

  1. Windows version you’ve got.
  2. If you are aware of automatic braille display detection in NVDA 2018.3 and later.
  3. Which port is BrailleNote connected to via Bluetooth (automatic or a COM port number).

I’m interested in this, as I do have an Apex and recently introduced Apex BT scroll wheel and BrailleNote QT support to NVDA in 2018.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michael Munn
Sent: Thursday, October 18, 2018 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth

 

The Apex model of the Braille Note is no longer supported by Humanware.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Michael Munn
 

The Apex model of the Braille Note is no longer supported by Humanware.


Stopping sapi5 voices from long pauses?

Matt Turner
 

Hi folks, subject says it all.

I think someone on this list figured it out, but can't remember.

These are the sapi5 voices in windows.


Re: accessing notifications in windows 10 1809

David Moore
 

Hi!

The new key command for getting to a notification is:

Windows+Shift+V!

Just add the Shift!

David Moore

 

                                                                                                                                                                                                                Sent from Mail for Windows 10

 

From: abdul muhamin
Sent: Thursday, October 18, 2018 4:13 PM
To: nvda@nvda.groups.io
Subject: [nvda] accessing notifications in windows 10 1809

 

Hi guys, how do I access notifications, specially skype call while I’m out of focus, because if I press win plus v, it opens the clipboard history, instead of open that notification, hoping for solution, thanks

 

Sent from Mail for Windows 10

 

 


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Armando Maldonado
 

It worked using both methods in previous releases of NVDA and the reason I would like to go bluetooth is USB times out after a while, thanks.

----- Original Message -----
From: "Antony Stone" <antony.stone@nvda.open.source.it>
To: <nvda@nvda.groups.io>
Sent: Thursday, October 18, 2018 2:09 PM
Subject: Re: [nvda] BrailleNote Apex will no work with latest NVDA and Bluetooth


Firstly I would ask whether it worked with a previous version of NVDA, or is
this the first version you're trying to connect it with?

Secondly I would ask whether it works using USB, or whatever alternative
connection it supports other than Bluetooth.


Antony.

On Thursday 18 October 2018 at 22:55:46, Armando Maldonado wrote:

Hello,
I'm trying to connect my brailleNote Apex with latest NVDA release and no
matter what HumanWare Braillenote driver I choose I get a Cannot load
Braille driver error. How can I remedy this issue and how can I save this
so NVDA can remember which display to use so it will not revert to No
Braille? Thanks. Armando
--
I conclude that there are two ways of constructing a software design: One way
is to make it so simple that there are _obviously_ no deficiencies, and the
other way is to make it so complicated that there are no _obvious_
deficiencies.

- C A R Hoare

Please reply to the list;
please *don't* CC me.


Re: BrailleNote Apex will no work with latest NVDA and Bluetooth

Antony Stone
 

Firstly I would ask whether it worked with a previous version of NVDA, or is
this the first version you're trying to connect it with?

Secondly I would ask whether it works using USB, or whatever alternative
connection it supports other than Bluetooth.


Antony.

On Thursday 18 October 2018 at 22:55:46, Armando Maldonado wrote:

Hello,
I'm trying to connect my brailleNote Apex with latest NVDA release and no
matter what HumanWare Braillenote driver I choose I get a Cannot load
Braille driver error. How can I remedy this issue and how can I save this
so NVDA can remember which display to use so it will not revert to No
Braille? Thanks. Armando
--
I conclude that there are two ways of constructing a software design: One way
is to make it so simple that there are _obviously_ no deficiencies, and the
other way is to make it so complicated that there are no _obvious_
deficiencies.

- C A R Hoare

Please reply to the list;
please *don't* CC me.


BrailleNote Apex will no work with latest NVDA and Bluetooth

Armando Maldonado
 


Hello,
I'm trying to connect my brailleNote Apex with latest NVDA release and no matter what HumanWare Braillenote driver I choose I get a Cannot load Braille driver error. How can I remedy this issue and how can I save this so NVDA can remember which display to use so it will not revert to No Braille? Thanks.
Armando


Re: NVDA with Links and Attachments Continued

Gene
 

Proofreading a message is not the same as receiving a message.  Proofreading a message being composed will usually not show links as links, as far as I know.  As far as I know, this is JAWS doing what a screen-reader shouldn't do, pretending something is being shown as a link when it isn't and is just text as far as a sighted person reading a message they are composing is concerned.  But if I'm wrong, I hope to be corrected.  I've never checked this.  But JAWS didn't used to announce link and NVDA doesn't. 
 
If someone receives a message from you and you have written a link properly, www.rest of link or http://www.rest of link, if that person doesn't see the structure as a linkk, that's their problem.  Maybe they are reading mail as plain text and maybe their e-mail program doesn't show mail as a link in plain text.
 
Gene

----- Original Message -----
Sent: Thursday, October 18, 2018 2:12 PM
To: nvda
Subject: [nvda] NVDA with Links and Attachments Continued

Hello Everyone,

Gene, I understand what you are saying about links and will send
myself a test message. However, If I copy and paste a YouTube link, or
a specified URL is typed in an email, as I proof-read my email,
oftentimes the word 'link' will not be heard with the URL. In some
cases, people have told me that the URL did not get received by them
as a link, only the URL itself. Moreover, the same is observed to
occur on Facebook.
Test:
www.abc.com

At one point in the past, it seems typed URL's did automatically
appear with a link in one's email and not too terribly long ago..
I'll send this communication to myself as well, thank you.

--
David Russell
david.sonofhashem@...



Re: NVDA STOPS SPEAKING RANDOMLY

Gene
 

Before you ran all these maintenance programs, did you try rebooting?  These programs have nothing to do with the CPU load.  The CPU load is determined by the number of processes running and how much computer resources they use.
 
Diksk Cleanup removes unused and unneeded files like temporary files.  Defrag moves files and parts of files that make up one file closer together so the hard drive doesn't have to do as much work to get the information since it is close together.  But none of this has to do with the processor load.
 
I'm telling you this to help you understand what these programs do and because it is inefficient and useless to do unnecessary maintenance.  I'm not sure how this is done and others may tell you, but you can use the Task Manager to get an idea of what programs are using a lot of computer resources. 
 
And, as I said, just rebooting may solve the problem.
 
Gene

----- Original Message -----
Sent: Thursday, October 18, 2018 1:42 PM
Subject: Re: [nvda] NVDA STOPS SPEAKING RANDOMLY

I had this problem a few days ago and wrote to the list about it. I
haven't experienced it since then. Some other trouble I had,
especially yesterday, was that my CPU was at an outrageous percentage.
I ran Disk Cleanup, Disk Defragmenter, and reorganized some files. And
I also uninstalled Malwarebytes. I'm not sure if any of these things
in particular helped, but both my problems seem to have disappeared. I
had a lot of large downloads, especially games. This is just a guess,
but maybe NVDA stops speaking because the CPU load is too high.
There's an add-on for NVDA called Resource Monitor. With that
installed, you can press insert+shift+1 and it will tell you the CPU
load.



On 10/18/18, Christo Vorster <christo@...> wrote:
> Hi Group
>
>
>
> I’m sorry if I missed messages regarding my problem, but I experience NVDA
> falling silent every now and then while I am working in MS W, MS Excel,
> Outlook, and even when I am playing some games. Regarding the games, I
> silence NVDA.
>
>
>
> I suddenly thought that it might not be a NVDA problem, but I’m not sure.
>
>
>
> I use a Del desktop computer with Windows 10, the latest update, MS Office
> 2016 and NVDA 2018.3.2.
>
>
>
> Regards
>
>
>
> Christo Vorster (Worcester, South Africa)
>
>
>
> Christo Vorster
>
> Programme Co-ordinator | Program Koördineerder
>
> 20 Adderley Street, Worcester
>
> T 023 348 7636 F 086 415 6839
>
> www.innovationfortheblind.org <http://www.innovationfortheblind.org>
>
>
>
>
>
>
>



Re: Abby fine reader 12

Gene
 

You may be able to correct the problem but do you care about saving formatting?  You can use control a to select all, copy it to the clipboard, then paste it into a word processor or Notepad.  You can then save the pasted document.  You can use Notepad if you just want a text file and you don't care about losing formatting.  If you save it as a word processor document, I don't know if you will lose formatting or if it will change.  Gene

----- Original Message -----
Sent: Thursday, October 18, 2018 1:26 PM
Subject: [nvda] Abby fine reader 12

I'm using abby fine reader 12. I'm not able to save file. If I press ctrl + s, nothing happens. When I attempt to close abby fine reader, it asks me I want to save or not. After pressing yes and doing everything when I press enter on save, it shows internal error. How to fix it?


accessing notifications in windows 10 1809

abdul muhamin
 

Hi guys, how do I access notifications, specially skype call while I’m out of focus, because if I press win plus v, it opens the clipboard history, instead of open that notification, hoping for solution, thanks

 

Sent from Mail for Windows 10