Date   

Re: Microsoft word question

Pranav Lal
 

Rui,
<snip As I said, the hotkey is NVDA+End.
PL] Many thanks. I checked the application specific hotkeys in the NVDA manual and was unable to find this hotkey. Where is it given?

Pranav


Re: Firefox 63 beta 64 and windows 7 64 not working again

Mr. Wong Chi Wai, William <cwwong.pro@...>
 

Brian , I am not commenting on you sorry for my misscommunication

Brian's Mail list account via Groups.Io 於 18/10/2018 2:59 寫道:

Not sure what you are talking about. I'm just saying that nvda is not working on that version here. That is a fact, and I was as annoyed as you about the way the thread went, but it was to some extent relevant to nvda, but not to the issue at hand!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Mr. Wong Chi Wai, William" <cwwong.pro@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, October 17, 2018 12:39 AM
Subject: Re: [nvda] Firefox 63 beta 64 and windows 7 64 not working again


Sorry, can all those unrelated nonsense discussion move to somewhere else?
I have problem following the core discussion here.

I here tested out Firefox beta 63 64bit on portableapps.com on my win 7 64 bit and everything seemed go fine.






Brian's Mail list account via Groups.Io 於 16/10/2018 18:58 寫道:
Yes this is your opinion, but it does not really add to the conversation of, is the new version broken or not on windows 7. 62 works fine here but not in its 32 bit guise as that too fails to be accessible on web pages.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, October 16, 2018 10:27 AM
Subject: Re: [nvda] Firefox 63 beta 64 and windows 7 64 not working again


Reguardless of what they say, firefox is crap.

Simply that they deem accessibility could be a security risk and will slow things down is my main reason not to trust mozilla anymore.

The only reason I use thunderbird is that I don't need to access the addons interface which is flat out crap and inaccessible but I don't need it.

New firefox is crap and will always have a bad reputation in my books.

Waterfox 56 seems to adopt both classic and new tech, and as long as we users can get the scripts for it it will be good.

There are a few downsides to it though.

The first is because of firefox 60 and up we will not get any more new addons ever for it and will have to run older versions of addons for ever.

Depending on what those are it may not matter in most cases, noscript works as it always has, nav sounds, privacy badger, and https everywhere just work and its all I really give a damn about.

I'd like it in ccleaner but as I have set it to never remember my history at all well who knows.

Its also not secured as often or updated as often, trying to stay as close to the esr versions as it can.

Right now its still showing firefox 56.

The authors say that it will eventually have to change and its getting rewritten and also that there is an addon store coming.

The users are happy though and I suspect the dev is taking his sweet time about any real change and is in no hurry.

If you really want a secure as up to date program waterfox is probably not for you chrome is good, though they have their own issue.

If you can stomach firefox then its your best bet to continue I guess.

But if like me you just want the same old net to work, waterfox just does that.

No tracking etc.

Ofcause you loose things like extra shields by default, and a few other things like internal app updates, and autoupdates by mozilla updaters.

It does update itself so I don't think that matters.





On 10/16/2018 9:35 PM, Brian's Mail list account via Groups.Io wrote:
Anyone tried Firefox 63 beta 64bit on windows 7?; I cannot get anything to read on the screens; it just says unknown.; Is this a bug in the Firefox beta?; If somebody could test other than myself then if it is; have a poke at Mozilla.; 62.03 seems to work fine here which is why I was concerned. I had to do a system restore in case the reason it fails is that its messed with the registry somehow.; Remember its windows 7 64. I am still keeping waterfox as default due to it having system sound capability. its about time Firefox built these in to their browser as well.; Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.








Tables are not recognized on a computer but are on another

Cleverson Casarin Uliana
 

Hi all, in both my computer at home and at my workplace, I use NVDA 2018.3.2, and the Waterfox browser 64-bit. The only difference is that here at home I have Windows 10 and at my workplace it is Windows 7. There at my workplace, NVDA recognizes a bigger number of tables while browsing the web than it recognizes here at home. There are several places in some pages where I can't use the control+alt+arrows commands to navigate the tables when I am at home, because NVDA says I'm not at a table cell. Then when I go to the same page there at my workplace, it recognizes such tables normally. I have confirmed that I am using the same settings related to tables at the NVDA document formating section. Do you have an idea what's the explanation for this please?

Thanks,
Cleverson


Re: Say all

Gene
 

In my last message, I should have said that if Word Wrap is already checked, press escape twice to get back to the main window and then close the program if you wish.
 
Gene

----- Original Message -----
From: Gene
Sent: Thursday, October 18, 2018 7:53 PM
Subject: Re: [nvda] Say all

What does it do with other text files?  I've seen something like this happen with this or that program at times but never as a general pattern in numerous programs.  There is no way to misconfigure this behavior.  It is a feature in NVDA and it can't be changed.  I'm not sure why you are having the problem. 
 
It may be that the text file is somehow not in proper form,  Try the following:
In Notepad, Open the menus.
Right arrow to format. 
Down arrow to Word Wrap. If you hear checked after word wrap is announced, there is nothing to do.  Press escape in that case to return to the main window and then close the program if you wish.  If you don't hear checked, press enter.  The menu will close and Word Wrap is now checked.  Now, open the file in Notepad and see if it reads properly.  While I don't think this will solve the problem, I can't think of any other possible solutions and this one might work.
 
Gene 
----- Original Message -----
Sent: Thursday, October 18, 2018 5:52 PM
Subject: [nvda] Say all

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: Say all

Gene
 

What does it do with other text files?  I've seen something like this happen with this or that program at times but never as a general pattern in numerous programs.  There is no way to misconfigure this behavior.  It is a feature in NVDA and it can't be changed.  I'm not sure why you are having the problem. 
 
It may be that the text file is somehow not in proper form,  Try the following:
In Notepad, Open the menus.
Right arrow to format. 
Down arrow to Word Wrap. If you hear checked after word wrap is announced, there is nothing to do.  Press escape in that case to return to the main window and then close the program if you wish.  If you don't hear checked, press enter.  The menu will close and Word Wrap is now checked.  Now, open the file in Notepad and see if it reads properly.  While I don't think this will solve the problem, I can't think of any other possible solutions and this one might work.
 
Gene 

----- Original Message -----
Sent: Thursday, October 18, 2018 5:52 PM
Subject: [nvda] Say all

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: Say all

Rui Fontes
 

Maybe some setting on screen duration?

NVDA, by itself, do not have any setting to that...

Rui


Às 23:52 de 18/10/2018, Vlad Dragomir escreveu:

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: Unable to read the edit field labels for the file properties in Microsoft Excel and Microsoft Word

David Apps
 

Dear Cearbhall

Thank you so much for confirming that. I am sorry for my delay in replying to your message. It took me a while before I had time to create the issue on GitHub:

https://github.com/nvaccess/nvda/issues/8855

Thank you again

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

________________________________


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