[nvda] Re: Proposed NVDA keyboard change
- From: "Timothy Wynn" <tmthywynn8@xxxxxxx>
- To: <nvda@xxxxxxxxxxxxx>
- Date: Wed, 30 May 2007 12:47:24 -0400
Couldn't you make a option for that as well?
----- Original Message -----
From: "James Teh" <jamie@xxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Tuesday, May 29, 2007 9:01 PM
Subject: [nvda] Re: Proposed NVDA keyboard change
Further to this:
Passing numpad insert through to the application if it is pressed and
released doesn't make a great deal of sense, as nothing else on the
numpad is passed through (they are all NVDA keys). However, we don't
want to make the behaviour of the modifier keys inconsistent; it just
gets too confusing otherwise. An alternative to the pass through
solution is to make a double tap of the key pass through to the
application; e.g. tap insert twice to press insert in the application,
caps lock twice to toggle capsl lock.
Jamie
Michael Curran wrote:
> Hi all,
>
> Jamie and I have been talking about how to solve this keyboard issue,
> where insert isn't available, or is not appropriate.
>
> We are thinking now that you will be able to choose whether specific
> keys will act as the NVDA modifier key. So, the choices will be
> capslock, extended insert, and nmpad insert.
>
> You can have at least one, or two, or all three.
>
> However, so that its easy to use the actual functionality of the
> application (what would happen when you normally press the key with out
> NVDA), if you press it and let go, with out pressing another key (to
> complete the command), the key will go through to the application.
>
> Some examples:
> You hold down capslock and tap the t key. It will speak the title of the
> application.
> You press the capslock key, but nothing else, it will toggle capslock on
> or off.
>
> However, keys like the insert keys do not normally give verbal feedback
> when they are passed through to the application, so we are thinking
> perhaps that if insert is pressed, and NVDA does nothing with it (its
> passed to the application) NVDA will say "insert" to let you know this.
>
> All these changes will be quite easy to do, we just need to know if
> people would be happy for it to be this way.
>
> Mick
>
>
> To post messages to the list send email to
> nvda@xxxxxxxxxxxxx
> To modify your NVDA Email settings go to:
> http://www.freelists.org/list/nvda
> Thank you for your continued support of Nonvisual Desktop Access, an
> open source free screen reader for Microsoft Windows:
> http://www.nvda-project.org/
> To get the latest NVDA snapshot:
> http://www.nvda-project.org/snapshots/
> Report bugs or make feature requests at:
> http://trac.nvda-project.org/
> Message Archive:
> http://www.freelists.org/archives/nvda
--
James Teh
Email: jamie@xxxxxxxxxxx
WWW: http://www.jantrid.net/
MSN Messenger: jamie@xxxxxxxxxxx
Jabber: jteh@xxxxxxxxxx
Yahoo: jcs_teh
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
- Follow-Ups:
- [nvda] Re: Proposed NVDA keyboard change
- From: James Teh
- References:
- [nvda] Proposed NVDA keyboard change
- From: Michael Curran
- [nvda] Re: Proposed NVDA keyboard change
- From: James Teh
Other related posts:
- » [nvda] Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- » [nvda] Re: Proposed NVDA keyboard change
- [nvda] Re: Proposed NVDA keyboard change
- From: James Teh
- [nvda] Proposed NVDA keyboard change
- From: Michael Curran
- [nvda] Re: Proposed NVDA keyboard change
- From: James Teh