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

Add "report formatting under cursor routing key" command #7106

Closed
dkager opened this Issue Apr 26, 2017 · 9 comments

Comments

Projects
None yet
5 participants
@dkager
Copy link
Collaborator

dkager commented Apr 26, 2017

See #7097 (comment)

This would be the ideal action for the Alva BC6 and other displays with second cursor routing keys. On other displays it could be something like NVDA+routing.

Technical from @jcsteh:

From an implementation perspective, I think we'd need to add a method to get a TextInfo from a routing index. Duplicating formatting reporting code in both globalCommands and braille sounds ugly to me.

@jcsteh

This comment has been minimized.

Copy link
Contributor

jcsteh commented Apr 26, 2017

@dkager

This comment has been minimized.

Copy link
Collaborator Author

dkager commented Apr 26, 2017

When you say NVDA+routing, I assume you mean the NVDA key on the keyboard?

Yes, but your suggestion makes more sense indeed. This assumes displays and drivers can deal with combinations of keys plus routing.
CC @leonardder

@jcsteh

This comment has been minimized.

Copy link
Contributor

jcsteh commented Apr 26, 2017

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented May 16, 2017

Handy Tech does support this. I recall that the Baum driver doesn't, but that might be something which we can fix.

@jcsteh

This comment has been minimized.

Copy link
Contributor

jcsteh commented May 16, 2017

@dkager

This comment has been minimized.

Copy link
Collaborator Author

dkager commented May 16, 2017

I still think supporting e.g. NVDA+routing would be beastly awesome, but that's a topic for another day. Judging by this discussion it's OK to start with on-display key combinations for the issue at hand.

@jcsteh

This comment has been minimized.

Copy link
Contributor

jcsteh commented May 16, 2017

@dkager

This comment has been minimized.

Copy link
Collaborator Author

dkager commented May 17, 2017

This is all true. I just feel a bit bad for excluding those displays that don't support gestures with routing keys.

One use case from my earlier screen reader days was to use Shift+routing to select up to a certain point of text, e.g. in Notepad. But the only reason that required Shift was because the routing keys emulated actual mouse clicks AFAIK.

On the subject of reporting formatting, I'm still contemplating how to code this in a non-ugly way. :)

@jcsteh

This comment has been minimized.

Copy link
Contributor

jcsteh commented May 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.