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

Treat OpenBook as a self-voicing application #1209

Closed
nvaccessAuto opened this Issue Nov 19, 2010 · 8 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto
Copy link

nvaccessAuto commented Nov 19, 2010

Reported by RamboUdin on 2010-11-19 11:24
The good example is OpenBook. First, open openbook.
Expected: NVDA should be quite, so that openbook's speech can take place.
Actual: NVDA still speak.

So, i need to press insert+s to turn off speech. Then, when i'm done, i need to press insert+s again, to turn on speech.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Nov 21, 2010

Comment 1 by jteh on 2010-11-21 22:12
A specific change needs to be made for each of these self-voicing applications. There's no way for NVDA to know whether something is self-voicing. To do this for !OpenBook, we need the name of the !OpenBook executable.
Changes:
Changed title from "NVDA should quit it's speech when in application that have it's own voice" to "Treat OpenBook as a self-voicing application"
Milestone changed from None to None

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 11, 2012

Attachment obu.py added by Bernd on 2012-01-11 22:11
Description:
Appmodule for OpenBook

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 11, 2012

Comment 2 by Bernd on 2012-01-11 22:14
The attached file threads openBook as a self-voicing application. A german person who checked this appmodule told me that openBook isn't using the braille display if nvda is in sleep mode.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 11, 2012

Comment 3 by jteh on 2012-01-11 23:45
Committed in c6437f1 with minor additions by me. Thanks.
Changes:
Milestone changed from None to 2012.1
State: closed

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 12, 2012

Comment 4 by aleskis on 2012-01-12 00:32
In this particular case, rather to make heavy NVDA in adding successive appmodules, the ticket #667 make sense. Almost screenreaders provide a profile system, and not because it's a gadget, but because each group of application bring a particular situation. I could give you three or four specific scenario necessiting this functionnality, if necessary.
Please consider again this suggestion, asked since longtime by a lot of people.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 12, 2012

Comment 5 by jteh on 2012-01-12 01:00
Profiles wouldn't have solved this ticket any better than tiny app modules. Distributing application specific profiles with NVDA would be the same as distributing tiny app modules. Other arguments in support of profiles should be discussed in #667, but this argument is not a strong use case.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 12, 2012

Comment 6 by briang1 on 2012-01-12 07:11
So are we now invited to suggest other self voicing applications and if available submit min app modules for inclusion as in the case of Open Book. I always assumed that guide and cicero to name but two, can be used by users, but were not being considered for inclusion in the main distribution. Lots of people seem to be using Cicero in the UK, and also i think some support of Windows outside Guide might be very handy. I have copies of both app modules, though Guide seems to have two executables so needs two files.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 12, 2012

Comment 7 by jteh on 2012-01-12 07:20
So long as it makes sense to enable sleep mode for the app for all users (i.e. it isn't just a small portion of the user base that wants this), it will almost certainly be accepted for inclusion. Please file separate enhancement tickets for these.

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.