https://bugzilla.novell.com/show_bug.cgi?id=713313 https://bugzilla.novell.com/show_bug.cgi?id=713313#c1 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ke@suse.com Component|Translations |YaST2 AssignedTo|ke@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|ke@suse.com |jsrain@suse.com --- Comment #1 from Karl Eichwalder <ke@suse.com> 2011-08-30 09:22:20 CEST --- This behavior is probably a side-effect of the implementation. The "Next" button is translated only once (base.pot)--at least, that's the theory. It might be worth to check from time to time, whether that's actually the case. If there are more buttons than the "Next" button in a single dialog that want the "N" as a shortcut, the shortcut resolver kicks in and does a reassignment on it's own. Maybe, it is possible to enhance the resolver somehow? What about an exception list? Or reassign the first occurrence (I think, the standard buttons always come at the end of a dialog). It is not the first time that a user complains about the current implementation. Thus I vote to think about an improvement. Another less confusing solution would be to give up on the resolver completely and just set the focus on the first button with the "_N"; if the user presses Alt-N a second time, move the focus to the next "_N". Then, if the user wants to execute the action, he can either press Space or Enter. I think, this is how all the other GUIs behave. I'm not sure who can help with this usability issue... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.