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
Status bar handling: allow app modules to define their own routines to fetch status bar and use it in status bar command in global commands #4640
Comments
Comment 1 by jteh on 2014-11-22 04:52 Out of interest, does Vim actually have a status bar object? If so and it's at the bottom of the screen, you just need to give it ROLE_STATUSBAR. If not, where does the status bar information come from? |
Comment 2 by lpintes (in reply to comment 1) on 2014-11-22 08:14
The Gvim has a window which tries to simulate the console. So there is no status bar object. I need to parse the displayText property and extract the last line. |
Comment 3 by jteh on 2014-12-01 04:46 |
Comment 4 by lpintes (in reply to comment 3) on 2014-12-01 08:12 |
Comment 5 by jteh (in reply to comment 4) on 2014-12-01 09:47
It's worth noting that displayText is also display model. :)
There doesn't have to be a separate object in this case. Even so, it should just be saying blank. I see that script still uses flatReviewPosition, where it should probably instead use review.getScreenPosition.
Interesting. How many blank lines are there after the status line? |
Comment 6 by lpintes (in reply to comment 5) on 2014-12-01 10:19
I noticed four things here:
But the thing I reported, i.e. it is impossible to go directly to the bottom of the flat review, because NVDA is stuck on something "blank" is true in any case. |
@LeonarddeR, @josephsl, @jcsteh any updates on this issue? |
Hi, We may need to gather more data before proceeding with this. Thanks. |
1 similar comment
Hi, We may need to gather more data before proceeding with this. Thanks. |
What type of data?
Rui Fontes
NVDA portuguese team
Às 23:48 de 04/01/2019, Joseph Lee escreveu:
… Hi,
We may need to gather more data before proceeding with this. Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4640 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APIHxkXFGkDmmLwloHNMKFSE2BRqNXb-ks5u_-hSgaJpZM4OZAN2>.
|
Hi, data such as different status bar implementations, more feedback from the community and what not. Thanks.
|
…ken over after abandoned #12371 (#12845) Fixes #6769 Superseedes #12371 Summary of the issue: Currently, the Window File Explorer cannot be retrieved using the reportStatusLine global command. Description of how this pull request fixes the issue: • Take advantage of Status bar handling: allow app modules to define their own routines to fetch status bar and use it in status bar command in global commands #4640 to implement custom status bar retrieval by the explorer app module. • Use a UIAWalker to retrieve it, as hinted by @josephsl in Can't read status bar in File Explorer (Windows 10) #6769 (comment) • Still, instead of overlaying the status bar of its children for concerns expressed in Can't read status bar in File Explorer (Windows 10) #6769 (comment), allow app modules to provide their custom implementation of api.getStatusBarText • Implement explorer.AppModule.getStatusBarText as inspired by @ruifontes prototype in Nvda utters unavailable after copying files #6842 (comment) (hinted by @feerrenrut in Can't read status bar in File Explorer (Windows 10) #6769 (comment)) but in a slightly more complex way - trying to cover more unexpected cases.
Reported by nvdakor on 2014-11-21 19:15
Hi,
Some developers at NVDA development list proposes the following:
As there are situations where one may wish to emulate a status bar and/or read a particular status bar when an app has more than one status bar, let NVDA query the app module for a routine for fetching the desired status bar object before resorting to using status bar routine defined in API module. If this is implemented, it would open new possibilities for app modules to specify which status is which or provde a "fake" status bar. Some of the possibilities are:
This second scenario would allow an app module like that of Vim to let the user hear important status information using a familiar command.
Implementation strategies and current situation:
Thanks.
The text was updated successfully, but these errors were encountered: