Allow user to copy configuration to be used on secure desktops #730

Closed
nvaccessAuto opened this Issue Jun 25, 2010 · 9 comments

2 participants

@nvaccessAuto

Reported by elliott94 on 2010-06-25 14:17
Currently, NVDA uses ESpeak on the Windows logon screen. I'm not sure if this could be done, but it would be good if the users default synth could be used (SAPI 4, etc).

@nvaccessAuto

Comment 1 by jteh on 2010-06-26 23:27
The secure desktops are not tied to a specific user, so there is no "user" to use as context. To put it another way, you can't use the user's default synthesiser because there is no user to speak of here.
Changes:
Added labels: invalid
State: closed

@nvaccessAuto

Comment 2 by elliott94 on 2010-06-30 14:57
Would it not be possible to allow the user to define spasific options for speech settings, etc that could be used on this screen?
I'm just trying to understand how JFW uses the same speech rate as it does when you're logged into Windows.

@nvaccessAuto

Comment 3 by jteh on 2010-07-01 03:44
You can actually change the settings on a secure desktop and save them from there as you would for a normal user.

@nvaccessAuto

Comment 4 by elliott94 on 2010-07-01 15:01
Oh, that's good to know.
Just out of interest, when these new settings are applied, where will they be saved?
Cheers.

@nvaccessAuto

Comment 5 by jteh (in reply to comment 4) on 2010-07-02 05:49
Replying to elliott94:

Just out of interest, when these new settings are applied, where will they be saved?

It is saved in the system profile which is used for stuff that runs as the system user.

@nvaccessAuto

Comment 6 by elliott94 on 2010-07-03 22:36
Hi,
Ok, this makes sence.
I'm wondeirng, however, do you know where this folder can be located?
I'm trying to use Eloquence on these Secure screens, but obviously need to copy the driver to the correct location.
Thanks a lot.

@nvaccessAuto

Comment 7 by elliott94 on 2010-08-07 09:38
Fixed in main:changeset 3690.
Changes:
Changed title from "NVDA could use the users default synth on the logon screen" to "NVDA could use the users configuration settings on logon and Secure Desktop screens"
Removed labels: invalid
State: reopened

@nvaccessAuto

Comment 8 by elliott94 on 2010-08-07 09:39
Changes:
State: closed

@nvaccessAuto

Comment 9 by jteh on 2010-08-07 12:39
Changes:
Changed title from "NVDA could use the users configuration settings on logon and Secure Desktop screens" to "Allow user to copy configuration to be used on secure desktops"

@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2010.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment