Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accidentally disconnect USB cabled Seika Notetaker Braille display and reconnect needs restart NVDA #13143

Open
moyanming opened this issue Dec 7, 2021 · 6 comments

Comments

@moyanming
Copy link
Contributor

Steps to reproduce:

  1. Start NVDA 2021.3RC1
  2. Connect the Seika Notetatker by USB cable
  3. Select "Seika Notetaker" in the Braille display of NVDA and connect successfully.
  4. Accidentally disconnect USB cable of Seika Notetaker.
  5. Reconnect the USB cable of Seika Notetaker, but NVDA can't connect automatically.
  6. Restart NVDA and Seika Notetaker connected automatically and works fine.

Here is the log accidentally disconnect.log
OSError: [WinError 1167] 设备没有连接。
"设备没有连接" means the device is not connected.

Windows version:

Windows 10 1901 Pro

@moyanming
Copy link
Contributor Author

I have tested this build, but this issue has not been fixed yet.
Here is the log:
accidentally disconnect.log

@seanbudd
Copy link
Member

seanbudd commented Jul 4, 2022

Is this fixed in 2022.1? Was this fixed by #13191, #13142?

@cary-rowen
Copy link
Contributor

@seanbudd
Hello, I tested with the latest alpha-25756 and it is not fixed.

@moyanming
Copy link
Contributor Author

Is this fixed in 2022.1? Was this fixed by #13191, #13142?

Hi @seanbudd
I have tested NVDA 2022.2 and this issue is not fixed yet.

@CyrilleB79
Copy link
Collaborator

@moyanming, there has been a significant rework of brialle in last NVDA versions. Is this issue still present?

@moyanming
Copy link
Contributor Author

@moyanming, there has been a significant rework of brialle in last NVDA versions. Is this issue still present?

Hi @CyrilleB79 ,
I have tested the Seika Notetaker with NVDA 2024.1, this issue still no fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants