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

Review cursors don't see refreshed information #5771

Closed
ghost opened this issue Feb 22, 2016 · 15 comments
Closed

Review cursors don't see refreshed information #5771

ghost opened this issue Feb 22, 2016 · 15 comments

Comments

@ghost
Copy link

ghost commented Feb 22, 2016

When using a text mode program from the Windows terminal, often one must look at previous lines and this requires using review mode. However, if the review is on a given line, this line changes, and I press num+8, the line that will be read out will correspond to the old information. So when a program is refreshing data it can't be easily seen by review. This is especially annoying when using Braille output.

Would it be possible to fix this? It would be equivalent functionality to, say, JAWS invisible cursor.

@jcsteh
Copy link
Contributor

jcsteh commented Feb 22, 2016 via email

@ghost
Copy link
Author

ghost commented Feb 22, 2016

Yes, I mean on the command prompt. Typing characters on the focus does seem to work, but I mean using a program like BitchX, the line above the typing prompt (where the cursor and the focus are) contains state information (time, number of users in a given channel, etc). If I press 7 to move to it on review, and wait there, the changes on the line don't show on Braille output, and if I press num+8 the stale information is spoken. If I press num+7 and then num+9, going up and down, that does seem to refresh it.

@jcsteh
Copy link
Contributor

jcsteh commented Feb 22, 2016

This is odd. I just tested this with the Linux top utility, and I definitely see, for example, the CPU percentage get updated.

@ghost
Copy link
Author

ghost commented Feb 24, 2016

You're right, I misunderstood what was going on. The problem is only with the Braille output when tethered to review. Pressing 8 reads the updated information but the braille display does not show it until there's user action like pressing any of the review commands that move the review. 8,5 or 2 don't seem to cause it to update, nor does it update by itself.

@jcsteh
Copy link
Contributor

jcsteh commented Feb 24, 2016

Ah. That makes sense. Thanks for the update.

@jcsteh jcsteh added this to the 2016.2 milestone Feb 24, 2016
@dkager
Copy link
Collaborator

dkager commented Feb 26, 2016

Interesting. The Windows console works well for me, though admittedly I don't run many programs that update instead of append text. In PuTTY I did notice today that if you run a command that updates a status line, braille doesn't update at all unless you move the review cursor off and back onto the line.

To reproduce I ran (on Unix): wget -O /dev/null http://ipv4.download.thinkbroadband.com/1GB.zip
The line with download status is shown in both focus mode and review mode but isn't updated. I'm not sure if the alternative of always showing updates is to be preferred, though. This would only be useful if the braille display didn't constantly pan back to the start of the line, which I believe in NVDA it wouldn't.

@jcsteh jcsteh modified the milestones: 2016.2, 2016.3 Apr 11, 2016
@jcsteh jcsteh removed this from the 2016.3 milestone Aug 5, 2016
@Adriani90
Copy link
Collaborator

@Eleuteri, @dkager is this issue still reproducible? Is it also occuring when the tetering is automatic?

@Adriani90
Copy link
Collaborator

cc: @LeonarddeR

@LeonarddeR
Copy link
Collaborator

I recall @bramd complaining about this.

@dkager
Copy link
Collaborator

dkager commented Feb 12, 2019

Indeed. Automatic tethering implies tethering to review, so that makes no difference.

@Adriani90
Copy link
Collaborator

I think this is fixed by #15163. @burmancomp, @LeonarddeR is this correct? In this case I think we can close it.

@burmancomp
Copy link
Contributor

Likely, at least as to @dkager tested in Unix.

@LeonarddeR
Copy link
Collaborator

It looks like this issue also mentions speech, so I'm not sure whether this is really fixed. It looks more like text changes not being picked up.

@jcsteh
Copy link
Contributor

jcsteh commented Sep 7, 2023

It mentioned speech initially, but #5771 (comment) corrects this as a misunderstanding.

@LeonarddeR
Copy link
Collaborator

AH, I missed that, I"m sorry,
In that case, lets close this, as I'm pretty sure this was indeed fixed. If not, we can always reopen or even better, create a new issue.

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