-
-
Notifications
You must be signed in to change notification settings - Fork 614
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
Comments
Are you talking about Windows command consoles? For me, review always
updates. For example, if I'm at a command prompt and I type some
characters, pressing numpad8 will report the prompt plus those characters.
If this isn't what you mean, please provide exact steps to reproduce.
|
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. |
This is odd. I just tested this with the Linux top utility, and I definitely see, for example, the CPU percentage get updated. |
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. |
Ah. That makes sense. Thanks for the update. |
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): |
cc: @LeonarddeR |
I recall @bramd complaining about this. |
Indeed. Automatic tethering implies tethering to review, so that makes no difference. |
I think this is fixed by #15163. @burmancomp, @LeonarddeR is this correct? In this case I think we can close it. |
Likely, at least as to @dkager tested in Unix. |
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. |
It mentioned speech initially, but #5771 (comment) corrects this as a misunderstanding. |
AH, I missed that, I"m sorry, |
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.
The text was updated successfully, but these errors were encountered: