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

When performing say all in the log viewer cared isn't following spoken text. #9179

Closed
lukaszgo1 opened this issue Jan 21, 2019 · 4 comments · Fixed by #13971
Closed

When performing say all in the log viewer cared isn't following spoken text. #9179

lukaszgo1 opened this issue Jan 21, 2019 · 4 comments · Fixed by #13971

Comments

@lukaszgo1
Copy link
Contributor

Steps to reproduce:

  1. open log viewer.
  2. perform say all.
  3. stop say all after some lines, and check caret location with NVDA+up arrow.

Actual behavior:

Caret is in the place from which you've started reading.

Expected behavior:

Caret should follow like in the notepad or MS Word.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2018.4.1 tested also with recent Alpha.

Windows version:

Windows 7

Name and version of other software in use when reproducing the issue:

None

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

Yes

Have you tried any other versions of NVDA?

Back to 2017.1 the issue was present in every version

@zahra21
Copy link

zahra21 commented Mar 21, 2020

hello.
i tested with nvda 2017.3 on windows xp two times and i could not reproduce the issue.

@feerrenrut
Copy link
Contributor

Rather than fix this log viewer issue, my preference would be to replace the log viewer with the following:

  • A read only text box for 'devInfo'
  • A button to open the log file in a default text editor.
    • Text editors such as Notepad++ have auto/manual refresh functionality, and the ability to save a copy of the file.
  • A command to open the log in default editor directly so users can override the NVDA+F1 shortcut if they wish.

@michaelDCurran @jcsteh @LeonarddeR any opinion on this?

@lukaszgo1
Copy link
Contributor Author

@feerrenrut I've used log viewer just as a convenient example. This problem occurs with most wx.TextCtrl's which I've seen in the wild - it is particularly problematic in apps used for reading longer texts such as QRead.

@feerrenrut
Copy link
Contributor

Ah, thanks for pointing that out @lukaszgo1

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