Bug 190290 - [KeyBindings] Please provide a way to search for unbound keys
Summary: [KeyBindings] Please provide a way to search for unbound keys
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: Other All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-31 13:43 EDT by Stefan Xenos CLA
Modified: 2019-09-06 16:08 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Xenos CLA 2007-05-31 13:43:18 EDT
Sometimes I want to bind a key to an unbound command. If you're using an RCP app with a lot of bindings, it can be hard to find an unused key sequence. 

It would be nice if the keys preference page had a "Browse..." button (next to the field where you enter the binding) that let you browse unused keys and pick one to assign to the command. The browser only needs to browse one keystroke at a time. Multi-keystroke bindings can be browsed by clicking browse two or more times.
Comment 1 Dani Megert CLA 2007-09-27 12:01:31 EDT
This is also something I run into each time I want to bind a command in a new workspace. The problem is that 'Include unbound commands' is off by default and hence when I type the name into the filter nothing is found.

Since performance is now acceptable I suggest to turn that thing on by default.

Also, it might be more intuitive if that checkbox would be place on the right side of the filter text entry field and renamed to [ ] Filter unbound commands (of course the default should then be off).
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:08:38 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.

If you have further information on the current state of the bug, please add it. 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.