Assign a gesture for the screen curtain by default

[LeonarddeR]

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
• NVDA + ctrl + f12
• NVDA + ctrl + printScreen

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.

[josephsl]

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> .

[ruifontes]

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>.

[dnz3d4c]

I agree with Control + NVDA + F12. I think it's a very good idea.

[beqabeqa473]

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

[k-kolev1985]

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

[beqabeqa473]

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

[LeonarddeR]

how about Control+NVDA+Print screen?

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!

[Brian1Gaff]

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)

[DrSooom]

@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.

[josephsl]

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> .

[ruifontes]

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>.

[josephsl]

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> .

[davidacm]

I like NVDA + control + f12.
Some laptops need fn key to press f12. But is a key easy to find because f12 is always in the same position.
PrintScreen doesn't have a standard position in laptop keyboards and most users doesn't know where to locate it.
In my personal case, I asigned NVDA + alt + c for this command.

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.

[Qchristensen]

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).