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

clash with the default NVDA Keystroke Ault Control N with Winamp. #2242

Closed
nvaccessAuto opened this issue Apr 13, 2012 · 11 comments
Closed

clash with the default NVDA Keystroke Ault Control N with Winamp. #2242

nvaccessAuto opened this issue Apr 13, 2012 · 11 comments

Comments

@nvaccessAuto
Copy link

Reported by Brendon22 on 2012-04-13 07:51
Hi, The keystroke that is used to start NVDA Ault Control N is a clash with the winamp keystroke to bring up moltable windows of Winamp. So can you please change the NVDA keystroke to something that doesn't clash with Winamp. Please Note: That this doesn't work on any Windows systdem but I've said in this ticket that it only afects Windows 7.

@nvaccessAuto
Copy link
Author

Comment 1 by dallasobrien on 2012-04-13 08:47
this is only a conflict if you have that ability turned on in winamp. this is not on by default in winamp when first installed. it is an option that must be enable manually.

@nvaccessAuto
Copy link
Author

Comment 2 by Brendon22 (in reply to comment 1) on 2012-04-13 09:28
Hi, Yes I know it's not a default setting when first putting Winamp onto computers, but that is the only way in Winamp to get moltable Winamp's to come up. And it can be very useful to have more than one Winamp up. So it's a problem with the keystroke. I call for the NVDA keystroke to kater for this!

@nvaccessAuto
Copy link
Author

Comment 3 by geoff on 2012-04-13 09:51
IMHO, I think this should be left as it is. The control-alt-n keystroke
is an obvious default for NVDA. This keystroke is assigned to the
shortcut on the desktop, so anyone experiencing this conflict can easily
change it in the properties for that icon.

This only affects users who wish to use a specific function of a
specific program. And the creation of this shortcut and keystroke can
even be turned off when installing NVDA, thereby avoiding the conflict
altogether.

Since it's almost impossible for NVDA to conflict with nothing, and
since it's possible for the user to change the key if they experience
this problem or to not have a key set up at all when installing, I vote
this ticket be closed as WontFix.
Changes:
Added labels: wontfix
State: closed

@nvaccessAuto
Copy link
Author

Comment 5 by jhomme on 2012-04-13 11:27
It sounds like the NVDA user could simply change the shortcut key property of the NVDA shortcut after they install NVDA.

@nvaccessAuto
Copy link
Author

Comment 6 by geoff (in reply to comment 2) on 2012-04-13 14:33
Replying to Brendon22:

Hi, Yes I know it's not a default setting when first putting Winamp onto computers, but that is the only way in Winamp to get moltable Winamp's to come up.

Actually it's not. If you enable multiple instances of Winamp, you can
simply open it multiple times and you'll get multiple copies... unless
something has changed very recently.

@nvaccessAuto
Copy link
Author

Comment 7 by Brendon22 on 2012-04-13 22:11
If I enable it that's the keystroke Ault Control N. So every time pressing Ault Control N A new coppy of NVDA will Lode? And Even opening one Winamp and then opening another Winamp pressing Ault and F4 will close them both down! So if the NVDA Keystroke was changed there wouldn't be this clash. And let's face it most blind people have Winamp on there computers :)
Changes:
Removed labels: wontfix
State: reopened

@nvaccessAuto
Copy link
Author

Comment 8 by jteh on 2012-04-14 09:01
Changing something as fundamental as this now would negatively impact far more users than the conflict with Winamp. "most blind people have Winamp on there computers" is a huge generalisation which isn't even particularly accurate. I know many users who don't use it. A work around has been provided; i.e. change the shortcut key yourself. The default will not be changed. This decision is final.
Changes:
Added labels: wontfix
State: closed

@nvaccessAuto
Copy link
Author

Comment 9 by peter on 2012-04-16 08:02
I have to say, that this is also a problem for all slovak users. Because shortcut ctrl+alt+n (altgr+n more precisely but altgr is an equivalent for ctrl+alt) is used to type } on slovak keyboard. I don't see it as a problem, but it is the fact, that all slovak users, who uses slovak keyboard probably changes shortcut as a first thing.

@nvaccessAuto
Copy link
Author

Comment 10 by jteh on 2012-04-16 08:35
See #2209 concerning the key not working for various locales. The solution there is to localise the default key.

@nvaccessAuto
Copy link
Author

Comment 11 by Brendon22 on 2012-05-25 09:09
Hi I'm reopening this ticket because there is another clash with the NVDA Keystroke Ault+Control+N. In MS Word 2010 to go to the draft option in word 2010. Wich is the best mode for Screen Readers. Wich is Ault+Control+N. It will not work in word 2010 it will bring up NVDA. And it will not do The word option. This only happends on Win 7. I think we should have to sepret check box options in the Installer. One: Wich ask's you The following: If you would like to have a shortcut for NVDA. Two: Another check box saying if you don't want a shortcut for NVDA. Three: an edit Field that you can type in your own shortcut that you would like for NVDA. So Like D and the computer is then smart enough to put the Ault+Control In-Front of the letter. Like when you go to the Properties options of a file and go to the Shortcut Edit Field. And if you didn't turn on the option for a Shortcut Key for NVDA. You don't get the edit field to type in the shortcut key that you want for NVDA.
Changes:
Removed labels: wontfix
State: reopened

@nvaccessAuto
Copy link
Author

Comment 12 by jteh on 2012-05-25 10:05
This doesn't change the situation. The reality is that this has been the NVDA start key for far too long to change it now. Besides, though I'm not sure about this particular command, there is an alternative way to access almost every command with a shortcut key in Word (ribbon, etc.). You can always change the key yourself via the shortcut properties if you wish.
Changes:
Added labels: wontfix
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant