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
Assign a gesture for the screen curtain by default #10560
Comments
Hi, how about Control+NVDA+Print screen? Thanks.
From: Leonard de Ruijter <notifications@github.com>
Sent: Friday, November 29, 2019 3:12 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [nvaccess/nvda] Assign a gesture for the screen curtain by default (#10560)
Is your feature request related to a problem? Please describe.
When introducing Screen Curtain, it was decided to add a global command for the curtain but leave it unassigned by default. Several people complained about this decision on NVDA-devel. As we now show a warning when initializing the screen curtain by default, I think apart from the question what key it should be, concerns about accidentally activating the curtain do no longer apply.
Describe the solution you'd like
Assign a gesture by default. Suggestions:
* NVDA + ctrl + slash
* NVDA + ctrl + semicolon
I'd rather not assign something to an alphanumeric character, though for symbols, we need to take keyboard layouts into account.
Describe alternatives you've considered
Leave as is.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#10560?email_source=notifications&email_token=AB4AXEHQ6CSLAY2PHWRZCJLQWD2JPA5CNFSM4JS6HUX2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H43TDHA> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4AXEE2BTYYKCHDOVK2WJTQWD2JPANCNFSM4JS6HUXQ> .
|
For me it is better, since is more universal through the various
keyboard layouts...
Only drawback: most people have no idea what what this key is
Rui Fontes
Às 11:14 de 29/11/2019, Joseph Lee escreveu:
… Hi, how about Control+NVDA+Print screen? Thanks.
From: Leonard de Ruijter ***@***.***>
Sent: Friday, November 29, 2019 3:12 AM
To: nvaccess/nvda ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [nvaccess/nvda] Assign a gesture for the screen curtain by
default (#10560)
Is your feature request related to a problem? Please describe.
When introducing Screen Curtain, it was decided to add a global
command for the curtain but leave it unassigned by default. Several
people complained about this decision on NVDA-devel. As we now show a
warning when initializing the screen curtain by default, I think apart
from the question what key it should be, concerns about accidentally
activating the curtain do no longer apply.
Describe the solution you'd like
Assign a gesture by default. Suggestions:
* NVDA + ctrl + slash
* NVDA + ctrl + semicolon
I'd rather not assign something to an alphanumeric character, though
for symbols, we need to take keyboard layouts into account.
Describe alternatives you've considered
Leave as is.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10560?email_source=notifications&email_token=AB4AXEHQ6CSLAY2PHWRZCJLQWD2JPA5CNFSM4JS6HUX2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H43TDHA>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4AXEE2BTYYKCHDOVK2WJTQWD2JPANCNFSM4JS6HUXQ>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10560?email_source=notifications&email_token=ADZAPRRWPSWMTMB2N2YAQK3QWD2S5A5CNFSM4JS6HUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFOTLSI#issuecomment-559756745>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZAPRRKIZ6IJH25HDFIFYDQWD2S5ANCNFSM4JS6HUXQ>.
|
I agree with Control + NVDA + F12. I think it's a very good idea. |
for me nvda+control+/ is ok.
…On 11/29/19, dnz3d4c ***@***.***> wrote:
I agree with Control + NVDA + F12. I think it's a very good idea.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#10560 (comment)
--
with best regards beqa
|
The drawback with keys such as slash, backslash, semicolon, period, comma, etc. is the fact that in some keyboard layouts such as "Bulgarian BDS/Typewriter", they may fail to work. And in such cases they have to be modified by the users or the translators of NVDA. That is why I prefer something like F12, Print Screen, etc. For example:
|
i don't think re-asigning a gesture for user or for translator is a big problem.
we have very good input gestures dialog nowadays.
…On 11/29/19, Kostadin Kolev ***@***.***> wrote:
The drawback with keys such as slash, backslash, semicolon, period, comma,
etc. is the fact that in some keyboard layouts such as "Bulgarian
BDS/Typewriter", they may fail to work. And in such cases they have to be
modified by the users or the translators of NVDA.
That is why I prefer something like F12, Print Screen, etc. For example:
- NVDA+Control+F12
- NVDA+Control+Print Screen
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#10560 (comment)
--
with best regards beqa
|
Might be problematic for some smaller laptops without a dedicated print screen key, though most of them have a print screen behind an fn combination. I will update the initial comment with all the listed suggestions. I like NVDA+control+f12 a lot! |
I don't think that is the point here. It needs to be something that works
out of the box in case a beginner wants it and having to remap it is often a
chore which is not needed in the other two cases, as long as the combination
has not already been grabbed by something else.
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "beqa gozalishvili" <notifications@github.com>
To: "nvaccess/nvda" <nvda@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>
Sent: Friday, November 29, 2019 1:05 PM
Subject: Re: [nvaccess/nvda] Assign a gesture for the screen curtain by
default (#10560)
…i don't think re-asigning a gesture for user or for translator is a big
problem.
we have very good input gestures dialog nowadays.
On 11/29/19, Kostadin Kolev ***@***.***> wrote:
> The drawback with keys such as slash, backslash, semicolon, period,
> comma,
> etc. is the fact that in some keyboard layouts such as "Bulgarian
> BDS/Typewriter", they may fail to work. And in such cases they have to be
> modified by the users or the translators of NVDA.
>
> That is why I prefer something like F12, Print Screen, etc. For example:
> - NVDA+Control+F12
> - NVDA+Control+Print Screen
>
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> #10560 (comment)
--
with best regards beqa
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#10560 (comment)
|
@LeonarddeR: Well, and not all small laptop keyboards contains all 12 F-keys. They could also be behind Fn. But there is a solution especially for this already in NVDA – keyboard layouts. Are NVDA+CTRL+Shift+S or NVDA+Shift+S already allocated? NVDA+S alone (Desktop layout) toggles between Speech off, Beep mode and Speech on. Thus it could be easier to memorize the Screen Curtain shortcut if it's similar to the one for toggling the speech modes. |
Hi, I imagine some add-ons took those keys already, hence the very reason for not assigning them in the first place at the moment. Thanks.
From: Daniel Mayr <notifications@github.com>
Sent: Friday, November 29, 2019 7:55 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [nvaccess/nvda] Assign a gesture for the screen curtain by default (#10560)
@LeonarddeR <https://github.com/leonardder> : Well, and not all small laptop keyboards contains all 12 F-keys. They could also be behind Fn. But there is a solution especially for this already in NVDA – keyboard layouts.
Are NVDA+CTRL+Shift+S or NVDA+Shift+S already allocated? NVDA+S alone (Desktop layout) toggles between Speech off, Beep mode and Speech on. Thus it could be easier to memorize the Screen Curtain shortcut if it's similar to the one for toggling the speech modes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#10560?email_source=notifications&email_token=AB4AXEDXLOMMXFLCBVFMWQ3QWHPZ5A5CNFSM4JS6HUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPYYTY#issuecomment-559909967> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4AXECOMNNKPWVFK2F7X2TQWHPZ5ANCNFSM4JS6HUXQ> .
|
Hello!
NVDA+Shift+S is already used by NVDA to togglr the suspension mode for
active application.
Às 03:55 de 30/11/2019, Daniel Mayr escreveu:
…
@LeonarddeR <https://github.com/leonardder>: Well, and not all small
laptop keyboards contains all 12 F-keys. They could also be behind Fn.
But there is a solution especially for this already in NVDA – keyboard
layouts.
Are NVDA+CTRL+Shift+S or NVDA+Shift+S already allocated? NVDA+S alone
(Desktop layout) toggles between Speech off, Beep mode and Speech on.
Thus it could be easier to memorize the Screen Curtain shortcut if
it's similar to the one for toggling the speech modes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10560?email_source=notifications&email_token=ADZAPRQB4OTHXEFFH5SN4K3QWHPZ5A5CNFSM4JS6HUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPYYTY#issuecomment-559909967>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZAPRXZ4LJ3B7MPJQ3PVZ3QWHPZ5ANCNFSM4JS6HUXQ>.
|
Hi, note that what is intuitive for one platform may not be that intuitive for those unfamiliar at first. Thanks.
From: Bill Dengler <notifications@github.com>
Sent: Monday, December 2, 2019 9:32 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [nvaccess/nvda] Assign a gesture for the screen curtain by default (#10560)
NVDA+shift+F11. Intuitive for Mac users.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#10560?email_source=notifications&email_token=AB4AXEATICHWZLINWLUHBDDQWXVLRA5CNFSM4JS6HUX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFYEKRI#issuecomment-561005893> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4AXECOQDAD5WDI5QSQI3LQWXVLRANCNFSM4JS6HUXQ> .
|
I like NVDA + control + f12. P.S: NVDA should have a feature to use "complex" key gestures to access the unfrequent options. E.G: NVDA + 0, f12 for screen curtain. |
Just a quick note that this is something users do request. I think, if we can find a suitable keystroke, that it would be worth assigning a default gesture to this. @davidacm Your P.S. would be worth opening a seperate issue for (I'm not arguing either way in saying that, just that this issue already has enough comments considering different keystrokes, your suggestion deserves its own space). |
Personally, I use Ctrl+NVDA+/ for this. This is convenient on US keyboards (and doesn't require function keys) but might be awkward on European layouts. |
Hi @Qchristensen, I will open a separate issue to talk about it. Best regards, David CM |
I am completely agnostic as far as what the keyboard shortcut is, but I definitely believe that NVDA should have a toggle shortcut assigned for this function as it "ships from the factory." |
To summarize there are objections for the following key proposals:
I agree with objection 1 and 2. At last I suggest a fifth possibility: There is no point in waiting some more years to find a shortcut key. Please give your opinion (especially on solution 3, 4 or 5) and I will try to submit a PR in the next weeks. I'll let at least two weeks before submitting the PR so that everyone can comment. |
My comment is that I don't find any of the objections particularly persuasive. Keyboards vary, period. Any user of any computer needs to know their own keyboard. I don't care whether a key is in a standard location or not, as if it needs to be used for something it's incumbent on the user to locate it on the keyboard or keyboards (as many laptop users attach external keyboards) that they are actually using. And that even includes if, on certain keyboard layouts for specific languages, an extra key press is needed to produce a seldom-used character. There is some keyboard shortcut, and I can't remember what for at the moment, that I have to use very infrequently that requires the asterisk. I have to remember to hit SHIFT + 8 on my keyboard to produce that asterisk when I need to use that shortcut. I agree with Cyrille regarding F12. I have not seen a laptop in years that does not have F1 through F12 keys, so I'd have no objection to some key combination that includes F12 in it. I'm not wild about the suggested use of Escape in combination with other keys, but would not strenuously object to it, either. It's well nigh impossible to screw up with a key combination that uses Escape if a 3-key-press combination is required. NVDA + Escape could work, too, as it's very unlikely for someone who uses NVDA to not know their NVDA key intimately and they're unlikely to ever hit it accidentally in combination with Escape. |
I essentially agree with @CyrilleB79.
I suggest NVDA+Control+Escape.
IMO this key combination should not be easy to accidentally hit, nor should it
be expected to be used frequently.
Thus a three key combo, and likely a two-handed combo.
I disagree, in part, with @britechguy's comments. Specifically, I think
objections 2 and 3(A), do have merit.
I believe we should avoid combinations including keys that might need the
involvement of FN. Those include function keys, and pause/prtscrn/similar.
FN is not a key which NVDA can detect, and using it in combination with the
NVDA key may be impossible in some circumstances, as the insert key itself may
change to something else when FN is in the picture.
Alternatively, if FN is required to use Insert, the function keys or other
special keys may then transform to something else, so it becomes next to
impossible to achieve the desired combination without an external keyboard.
FN opens up a whole pool of keyboard confusion that we shouldn't want to dive
into.
Escape, on the other hand, is escape all the time, even when FNed, at least on
all keyboards I've tested.
|
I disagree with the escape key, this suggest rather quiting something rather than starting something. Also if you set the same nvda key as narator key and start both screen readers, the nvda + escape is taken by narator to quit narator. In this case in my view people could by accident enable screen curtain while trying to quit narator while both screenreaders are running. |
I like solution 4 actually. |
@Adriani90 I don't think this is true. You can test it yourself by setting NVDA+Escape as your Screen Curtain key.
If you activate NVDA, turn on Screen Curtain, activate Narrator, and then press NVDA+Esc: Narrator completely intercepts this gesture.
That is the same reason you can not press Insert+q while running Narrator and NVDA, and expect it to quit NVDA.
Also, if you read a desktop item or other long string with both enabled, and press NVDA+esc, you will hear that Narrator shuts down, but NVDA does not even have its speech interrupted.
As for escape only exiting things not starting them: how do you explain Ctrl+Shift+Esc? Or Ctrl+Esc? (Task Manager and Start menu, respectively)
|
@XLTechie good points, thanks for that. in this case I agree also with the nvda+escape solution. |
Grouped answers:
I agree that every user needs to know their own keyboard and configure it for their needs when possible. But favoring standard location keys when possible is a significant plus when working on someone else's computer using NVDA on an USB stick (e.g. work with colleague, holidays in family, public libraries, etc.)
No, it does not work this way with punctuation. Let's imagine that NVDA+slash is defined as shortcut for screen curtain. On French keyboard the slash is not directly accessible but you need to press shift+colon. In this case unfortunately, neither pressing NVDA+colon or NVDA+shift+colon will trigger the screen curtain. French translators need to redefine this shortcut as NVDA+colon or NVDA+shift+colon in the French gesture file of NVDA. And even with this specific local configuration, the shortcut may not be adapted for people of other French speaking countries that are using NVDA in French but are using other keyboard layout such as French (Switzerland), French (Belgium) or Canadian standard multilingual. |
Hi, How about NVDA+9 to toggle screen curtain? Could we consider to use two keys commands, instead of three keys combination . Thanks. |
How about NVDA+9 to toggle screen curtain?
Personally, I would prefer if we stuck to the traditional use of number row keys
as frequently changed navigational function toggles. Bringing something like
screen curtain there, when it will probably only be used by a minority of users,
and does not fit the pattern of the usual functions of those keys, seems
questionable to me.
Could we consider to use two keys commands, instead of three keys combination .
Again, just personally, I prefer three keys because of the probable infrequency
of use. Thinking that other things that are more likely to be pressed many
times per day, may need the two key combos more.
But naturally there will be no satisfying everyone with whatever is ultimately
chosen; and everyone's usage will be different.
Something is better than nothing.
|
Agree. |
Closes #10560 Summary of the issue: The screen curtain is missing a default gesture (working out of the box). Users want to have a default gesture in order not to have to define one themselves. Description of user facing changes NVDA+control+escape is defined as default gesture. The gesture has been discussed in #10560: The main key is quite easy to find on a keyboard; e.g. PrintScreen is much harder because it's not always at the same place or sometimes behind Fn key. Usage of punctuation key for main key should be avoided because it differs from a local keyboard layout to another. Even if it may be translated by translators, the issue remains for people switching their keyboard layout. Punctuation keys are better suited for personal gestures. shortcut using 3 keys and not two due to the probable infrequency of use with respect to other gestures/commands with this gesture, there is no risk to activate the screen curtain by accident. Description of development approach Added in script's decorator and updated the documentation.
Sorry for being late to the discussion, but I still think NVDA + Shift + F11 should have been used. This is a standard gesture in Voiceover and Jaws also uses the F11 key. Shift and Escape is used to open the browser task manager, and Control + Shift + Escape is used to open the Windows task manager, which are very similar commands |
@brunoprietog, the current issue is now closed. You have also commented in #15590 (#15590 (comment)); unfortunately, your comment has not been answered explicitly by NV Access. Either you (or we) consider that the lack of explicit answer implicitely means that your proposal has not been accepted by NV Access. |
Is your feature request related to a problem? Please describe.
When introducing Screen Curtain, it was decided to add a global command for the curtain but leave it unassigned by default. Several people complained about this decision on NVDA-devel. As we now show a warning when initializing the screen curtain by default, I think apart from the question what key it should be, concerns about accidentally activating the curtain do no longer apply.
Describe the solution you'd like
Assign a gesture by default. Suggestions:
I'd rather not assign something to an alphanumeric character, though for symbols, we need to take keyboard layouts into account.
Describe alternatives you've considered
Leave as is.
The text was updated successfully, but these errors were encountered: