Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314269

Summary:	[QuickAccess] Key bindings shown in Quick Access dialog (Ctrl+3) do not work
Product:	[Eclipse Project] Platform	Reporter:	Dani Megert <daniel_megert>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	gautier.desaintmartinlacaze, markus.kell.r, prakash, psuzzi
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Dani Megert

2010-05-25 09:45:25 EDT

3.6 RC2.

Ctrl+3 now shows the key bindings next to the commands but they do not work. Either we have to
- make them work even when the Quick Access dialog is up
- not show them
- show them in a special color (gray is already used in the status line and the
  Ctrl+3 key binding in there does work)
- show a hint in the status line that they don't work while the dialog is shown

Comment 1 Dani Megert

2010-05-25 09:48:10 EDT

Not critical for 3.6.

Comment 2 Markus Keller

2010-05-25 10:26:35 EDT

I'd close this as WONTFIX. In OS menus, key bindings are also shown but don't work.

The Ctrl+3 is like the Keys preference page: It lists commands and their keybindings, but I wouldn't expect that the keys actually work while the dialog is up. Same in the Quick Assist popup when the table has focus.

And you would have to make sure all special cases are still useful:
Ctrl+3, Ctrl+F10 (bug 186048), Esc, Line Down (bug 237952), ...

Comment 3 Dani Megert

2010-05-25 10:32:44 EDT

>The Ctrl+3 is like the Keys preference page: It lists commands and their
>keybindings, but I wouldn't expect that the keys actually work while the dialog
>is up. 
Good point. The only confusion is probably that the same gray color is used in the status line. Maybe we could use a different color there (yes we'd have to align this with the other dialogs).

Comment 4 Eclipse Genie

2020-07-13 12:35:51 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.